Method for using a sensor to register a biometric for use with a transponder-reader system

ABSTRACT

A method for registering biometric information for use in a transponder-reader system is disclosed. The method includes steps of detecting, verifying and storing a proffered biometric sample. During detecting, a sensor detects a proffered biometric to obtain a biometric sample. During the verifying step, the biometric sample is compared with other stored samples and/or other information. During the storing step, the biometric sample is stored on a database, for use by the transponder-reader system in authorizing transactions.

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This invention is a continuation in part of U.S. Ser. No.10/340,352, filed on Jan. 10, 2003, and entitled “SYSTEM AND METHOD FORINCENTING PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT ANDCONTACTLESS TRANSACTIONS.” The '352 application itself claims priorityto U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM ANDMETHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT ANDCONTACTLESS TRANSACTIONS,” filed on Jul. 9, 2002 (which itself claimspriority to U.S. Provisional No. 60/304,216, filed on Jul. 10, 2001);U.S. patent application Ser. No. 10/318,432, entitled “SYSTEM AND METHODFOR SELECTING LOAD OPTIONS FOR USE IN RADIO FREQUENCY IDENTIFICATION INCONTACT AND CONTACTLESS TRANSACTIONS,” filed Dec. 13, 2002; U.S. patentapplication Ser. No. 10/318,480, entitled “SYSTEM AND METHOD FOR PAYMENTUSING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESSTRANSACTIONS,” filed December 13, 2002; and, U.S. Provisional PatentApplication No. 60/396,577, filed Jul. 16, 2002. All of the aboveapplications are hereby incorporated by reference.

FIELD OF INVENTION

[0002] This invention generally relates to a method for using a sensorto register biometrics for use with a transponder-reader system, andmore particularly, to using a sensor to register biometrics forbiometric security.

BACKGROUND OF INVENTION

[0003] Like barcode and voice data entry, RFID is a contactlessinformation acquisition technology. RFID systems are wireless, and areusually extremely effective in hostile environments where conventionalacquisition methods fail. RFID has established itself in a wide range ofmarkets, such as, for example, the high-speed reading of railwaycontainers, tracking moving objects such as livestock or automobiles,and retail inventory applications. As such, RFID technology has become aprimary focus in automated data collection, identification and analysissystems worldwide.

[0004] Of late, companies are increasingly embodying RFID dataacquisition technology in a fob or tag for use in completing financialtransactions. A typical fob includes a transponder and is ordinarily aself-contained device which may be contained on any portable formfactor. In some instances, a battery may be included with the fob topower the transponder. In which case the internal circuitry of the fob(including the transponder) may draw its operating power from thebattery power source. Alternatively, the fob may exist independent of aninternal power source. In this instance the internal circuitry of thefob (including the transponder) may gain its operating power directlyfrom an RF interrogation signal. U.S. Pat. No. 5,053,774, issued toSchuermann, describes a typical transponder RF interrogation systemwhich may be found in the prior art. The Schuermann patent describes ingeneral the powering technology surrounding conventional transponderstructures. U.S. Pat. No. 4,739,328, discusses a method by which aconventional transponder may respond to a RF interrogation signal. Othertypical modulation techniques which may be used include, for example,ISO/IEC 14443 and the like.

[0005] In the conventional fob powering technologies used, the fob istypically activated upon presenting the fob in an interrogation signal.In this regard, the fob may be activated irrespective of whether theuser desires such activation. Inadvertent presentation of the fob mayresult in initiation and completion of an unwanted transaction. Thus, afob system is needed which allows the fob user to control activation ofthe fob to limit transactions being undesirably completed.

[0006] One of the more visible uses of the RFID technology is found inthe introduction of Exxon/Mobil's Speedpass® and Shell's EasyPay®products. These products use transponders placed in a fob or tag whichenables automatic identification of the user when the fob is presentedat a Point of Sale (POS) device. Fob identification data is typicallypassed to a third-party server database, where the identification datais referenced to a customer (e.g., user) credit or debit account. In anexemplary processing method, the server seeks authorization for thetransaction by passing the transaction and account data to anauthorizing entity. Once authorization is received by the server,clearance is sent to the point of sale device for completion of thetransaction. In this way, the conventional transaction processing methodinvolves an indirect path which causes undue overhead due to the use ofthe third-party server.

[0007] A need exists for a transaction authorization system which allowsfob transactions to be authorized while eliminating the cost associatedwith using third-party servers.

[0008] In addition, conventional fobs are limited in that they must beused in proximity to the Point of Sale device. That is, for fobactivation, conventional fobs must be positioned within the area oftransmission cast by the RF interrogation signal. More particularly,conventional fobs are not effective for use in situations where the userwishes to conduct a transaction at a point of interaction such as acomputer interface.

[0009] Therefore, a need exists for a fob embodying RFID acquisitiontechnology, which is capable of use at a point of interaction device andwhich is additionally capable of facilitating transactions via acomputer interface connected to a network (e.g., the Internet).

[0010] Existing transponder-reader payment systems are also limited inthat the conventional fob used in the systems is only responsive to oneinterrogation signal. Where multiple interrogation signals are used, thefob is only responsive to the interrogation signal to which it isconfigured. Thus, if the RFID reader of the system provides only aninterrogation signal to which the fob is incompatible, the fob will notbe properly activated.

[0011] Therefore, a need exists for a fob which is responsive to morethan one interrogation signal.

[0012] Existing transponder-reader payment systems are additionallylimited in that the payment systems are typically linked to a fundingsource associated with the transponder which includes a predeterminedspending limit. Thus no flexibility is provided in instances where thepayment is requested which exceeds the predetermined spending limit.This is typically true in that traditional methods for processing arequested transaction involve comparing the transaction to the spendinglimit or to an amount stored in a preloaded value data file prior toproviding transaction authorization to a merchant.

[0013] Thus, a system is needed which processes transponder-readerpayment requests irrespective of the spending limit assigned to anassociated transponder-reader payment system funding source.

[0014] Further, traditional transponder-reader systems do not permit theuser to manage the system user account data. This is extremelyproblematic where the user wishes to change a transponder-reader systemfunding source to a source which provides more available spending room,or where changes are made to the user's status (e.g., change in address,phone number, email, etc.) for which the transponder-reader accountprovider wishes to readily update the user's account.

[0015] Thus a need exists for a transponder-reader system which willallow the user limited access to the transponder-reader account formanaging account data.

[0016] Further still, existing transponder-reader systems do not usuallypermit means for automatically incenting the use of the fob associatedwith the system as opposed to the credit or charge card associated withthe fob. That is, conventional transponder-reader systems do not providea means for encouraging usage of the transponder reader system byencouraging use of the fob product since the present systems do notsufficiently distinguish between usage of a system transponder and acharge or credit card account associated with the transponder.

[0017] Consequently, a need exists for a transponder-reader system whichis capable of determining when a system transponder is used, andproviding an incentive for such usage.

[0018] Still further, present systems are limited in that the systemsare unable to track credit or charge card usage and fob usage for asingle funding source. For example, in typical prior art systems, a fobmay be linked to a specified funding source (e.g., American Express,MasterCard, Visa, etc.) which may be used to provide funds forsatisfaction of a transaction request. The funding source mayadditionally have a consumer credit or charge card which may beassociated with the fob and which may be used for contact transactions.Where the credit or charge card is used, a statement reporting the cardusage is provided to the card user. However, the reporting statementdoes not include a reporting of the fob product usage. Thus, a fob useris unable to adequately chart, analyze or compare fob usage to the usageof the associated card. This is especially problematic where the fundingsource is used by more than one entity (e.g., spouses, multiple companypersonnel, etc.) or where one entity may use the fob and a separateentity may use the card associated with the fob.

[0019] Thus, a need exists for a transponder-reader payment system whichwould permit reporting of the fob usage and the credit card usage in asingle file.

SUMMARY OF INVENTION

[0020] Described herein is a system and method for using RFID technologyto initiate and complete financial transactions. The transponder-readerpayment system described herein may include a RFID reader operable toprovide a RF interrogation signal for powering a transponder system,receiving a transponder system RF signal, and providing transpondersystem account data relative to the transponder system RF signal. Thetransponder-reader payment system may include a RFID protocol/sequencecontroller in electrical communication with one or more interrogatorsfor providing an interrogation signal to a transponder, a RFIDauthentication circuit for authenticating the signal received from thetransponder, a serial or parallel interface for interfacing with a pointof interaction device, and an USB or serial interface for use inpersonalizing the RFID reader and/or the transponder. Thetransponder-reader payment system may further include a fob includingone or more transponders (e.g., modules) responsive to one or moreinterrogation signals and for providing an authentication signal forverifying that the transponder and/or the RFID reader are authorized tooperate within the transponder-reader payment system. In this way, thefob may be responsive to multiple interrogation signals provided atdifferent frequencies. Further, the fob may include a USB or serialinterface for use with a computer network or with the RFID reader.

[0021] The RFID system and method according to the present invention mayinclude a transponder which may be embodied in a fob, tag, card or anyother form factor (e.g., wristwatch, keychain, cell phone, etc.), whichmay be capable of being presented for interrogation. In that regard,although the transponder is described herein as embodied in a fob, theinvention is not so limited.

[0022] The system may further include a RFID reader configured to send astanding RFID recognition signal which may be transmitted from the RFIDreader via radio frequency (or electromagnetic) propagation. The fob maybe placed within proximity to the RFID reader such that the RFID signalmay interrogate the fob and initialize fob identification procedures.

[0023] In one exemplary embodiment, as a part of the identificationprocess, the fob and the RFID reader may engage in mutualauthentication. The RFID reader may identify the fob as including anauthorized system transponder for receiving encrypted information andstoring the information on the fob memory. Similarly, the fob, uponinterrogation by the RFID reader, may identify the RFID reader asauthorized to receive the encrypted and stored information. Where theRFID reader and the fob successfully mutually authenticate, the fob maytransmit to the RFID reader certain information identifying thetransaction account or accounts to which the fob is associated. The RFIDreader may receive the information and forward the information tofacilitate the completion of a transaction. In one exemplary embodiment,the RFID reader may forward the information to a point of interactiondevice (e.g., POS or computer interface) for transaction completion. Themutual authorization process disclosed herein aids in ensuring fobtransponder-reader payment system security.

[0024] In another exemplary embodiment, the fob according to the presentinvention, includes means for completing transactions via a computerinterface. The fob may be connected to the computer using a USB orserial interface fob account information may be transferred to thecomputer for use in completing a transaction via a network (e.g., theInternet).

[0025] In yet another exemplary embodiment of the present invention, asystem is provided which incents usage of the transponder-reader systemtransponder (e.g., fob). The system distinguishes between the usage of afob and the usage of a charge or credit card sharing the same fundingsource as the fob. Where the fob is used, the system may provideincentives to the user based on criteria predetermined by the fobissuer. Additionally, where a preloaded fob system is used, the presentinvention recognizes when the associated fob preloaded value data fileis loaded or reloaded with funds. The invention then may provide rewardpoints based on the criteria associated with the loading or reloadingaction. Further, the system according to this invention may incentpatronage of a merchant. In this case, the system may receive a fobtransaction request and incent the fob user based on a marker or otheridentifier correlated with the merchant. The marker may be included inthe transaction identification, in a merchant identification providedwith the transaction, or a combination of both.

[0026] In still another exemplary embodiment of the invention, a systemis disclosed which enables the fob user/owner to manage the accountassociated with the fob. The user is provided limited access to all or aportion of the fob account information stored on the account providerdatabase for updating, for example, demographic information, accountfunding source, and/or account restrictions (e.g., spending limits,personal identification number, etc.). Access to all or a portion of theaccount may be provided to the user telephonically, via a network (e.g.,online) or via offline communications. For example, the fob user may beprovided access to a system which has delayed communications with theaccount provider database wherein such a system may include, forexample, a kiosk which provides batch transmissions to the accountprovider system. In this way, the fob user/owner may update his accountinformation in real-time (e.g., telephonically or online) or at the timethe account provider receives the updated information (e.g., offline).

[0027] In a further exemplary embodiment, the present invention providesmethods for processing a transaction request whereby the amount of thetransaction request may be approved prior to requesting funding from thefunding source and/or verifying that the amount for completing thetransaction is available. In this way, the transaction may be approvedprovided the transaction and/or account meets certain predeterminedauthorization criteria. Once the criteria is met, the transaction isauthorized and authorization is provided to the requesting agent (e.g.,merchant). In one instance the payment for the transaction is requestedfrom the funding source simultaneously to, or immediately following, theproviding of the authorization to the merchant. In another instance, thepayment for transactions is requested at a time period later than whenthe authorization is provided to the merchant.

[0028] In yet another embodiment, a method for registering biometricinformation for use in a transponder-reader system is disclosed. Themethod includes steps of detecting, verifying and storing a profferedbiometric sample. During detecting, a sensor detects a profferedbiometric to obtain a biometric sample. During the verifying step, thebiometric sample is compared with other stored samples and/or otherinformation. During the storing step, the biometric sample is stored ona database, for use by the transponder-reader system in authorizingtransactions.

[0029] These features and other advantages of the system and method, aswell as the structure and operation of various exemplary embodiments ofthe system and method, are described below.

BRIEF DESCRIPTION OF DRAWINGS

[0030] The accompanying drawings, wherein like numerals depict likeelements, illustrate exemplary embodiments of the present invention, andtogether with the description, serve to explain the principles of theinvention. In the drawings:

[0031]FIG. 1A illustrates an exemplary RFID-based system in accordancewith the present invention, wherein exemplary components used for fobtransaction completion are depicted;

[0032]FIG. 1B illustrates an exemplary personalization system inaccordance with the present invention;

[0033]FIG. 2 is a schematic illustration of an exemplary fob inaccordance with the present invention;

[0034]FIG. 3 is a schematic illustration of an exemplary RFID reader inaccordance with the present invention;

[0035]FIG. 4 is an exemplary flow diagram of an exemplary authenticationprocess in accordance with the present invention;

[0036]FIG. 5 is an exemplary flow diagram of an exemplary decisionprocess for a protocol/sequence controller in accordance with thepresent invention;

[0037] FIGS. 6A-B are exemplary flow diagrams of a fob personalizationprocess in accordance with the present invention;

[0038] FIGS. 7A-B are exemplary flow diagrams of a RFID readerpersonalization process in accordance with the present invention;

[0039]FIG. 8 is a flow diagram of an exemplary payment/transactionprocess in accordance with the present invention;

[0040]FIG. 9 is another schematic illustration of an exemplary fob inaccordance with the present invention;

[0041]FIG. 10 is a depiction of an exemplary preloaded fobpayment/transaction process in accordance with the present invention;

[0042] FIGS. 11A-B are depictions of an exemplary preloaded fob accountreload process in accordance with the present invention;

[0043]FIG. 12 is a depiction of an exemplary Direct Linkpayment/transaction process in accordance with the present invention;

[0044]FIG. 13 is a depiction of another exemplary payment/transactionprocess in accordance with the present invention;

[0045]FIG. 14 is a depiction of an exemplary biometrics process inaccordance with the present invention;

[0046]FIG. 15 is another schematic illustration of an exemplary fob inaccordance with the present invention; and

[0047]FIG. 16 is another schematic illustration of an exemplary fob inaccordance with the present invention.

DETAILED DESCRIPTION

[0048] The present invention may be described herein in terms offunctional block components, screen shots, optional selections andvarious processing steps. Such functional blocks may be realized by anynumber of hardware and/or software components configured to perform tospecified functions. For example, the present invention may employvarious integrated circuit components, (e.g., memory elements,processing elements, logic elements, look-up tables, and the like),which may carry out a variety of functions under the control of one ormore microprocessors or other control devices. Similarly, the softwareelements of the present invention may be implemented with anyprogramming or scripting language such as C, C++, Java, COBOL,assembler, PERL, extensible markup language (XML), JavaCard and MULTOSwith the various algorithms being implemented with any combination ofdata structures, objects, processes, routines or other programmingelements. Further, it should be noted that the present invention mayemploy any number of conventional techniques for data transmission,signaling, data processing, network control, and the like. For a basicintroduction on cryptography, review a text written by Bruce Schneierentitled “Applied Cryptography: Protocols, Algorithms, and Source Codein C,” published by john Wiley & Sons (second edition, 1996), hereinincorporated by reference.

[0049] In addition, many applications of the present invention could beformulated. The exemplary network disclosed herein may include anysystem for exchanging data or transacting business, such as theInternet, an intranet, an extranet, WAN, LAN, satellite communications,and/or the like. It is noted that the network may be implemented asother types of networks, such as an interactive television network(ITN).

[0050] Where required, the system user may interact with the system viaany input device such as, a keypad, keyboard, mouse, kiosk, personaldigital assistant, handheld computer (e.g., Palm Pilot®, Blueberry®),cellular phone and/or the like). Similarly, the invention could be usedin conjunction with any type of personal computer, network computer,work station, minicomputer, mainframe, or the like running any operatingsystem such as any version of Windows, Windows NT, Windows 2000, Windows98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, Solaris or the like.Moreover, although the invention may frequently be described as beingimplemented with TCP/IP communications protocol, it should be understoodthat the invention could also be implemented using SNA, IPX, Appletalk,IPte, NetBIOS, OSI or any number of communications protocols. Moreover,the system contemplates, the use, sale, or distribution of any goods,services or information over any network having similar functionalitydescribed herein.

[0051]FIG. 1A illustrates an exemplary RFID transaction system 100A inaccordance with the present invention, wherein exemplary components foruse in completing a fob transaction are depicted. In general, theoperation of system 100A may begin when a fob 102 is presented forpayment, and is interrogated by a RFID reader 104 or, alternatively,interface 134. Fob 102 and RFID reader 104 may then engage in mutualauthentication after which the transponder 114 may provide thetransponder identification and/or account identifier to RFID reader 104which may further provide the information to the merchant system 130 POSdevice 110.

[0052] System 100A may include fob 102 having a transponder 114 and RFIDreader 104 in RF communication with fob 102. Although the presentinvention is described with respect to fob 102, the invention is not tobe so limited. Indeed, system 100 may include any device having atransponder which is configured to communicate with RFID reader 104 viaRF communication. Typical devices may include, for example, a key ring,tag, card, cell phone, wristwatch or any such form capable of beingpresented for interrogation.

[0053] RFID reader 104 may be configured to communicate using a RFIDinternal antenna 106. Alternatively, RFID reader 104 may include anexternal antenna 108 for communications with fob 102, where the externalantenna may be made remote to RFID reader 104 using a suitable cableand/or data link 120. RFID reader 104 may be further in communicationwith a merchant system 130 via a data link 122. System 100A may includea transaction completion system including a point of interaction devicesuch as, for example, a merchant point of sale (POS) device 110 or acomputer interface (e.g., user interface) 134. In one exemplaryembodiment the transaction completion system may include a merchantsystem 130 including POS device 110 in communication with RFID reader104 (via data link 122). As described more fully below, the transactioncompletion system may include user interface 134 connected to a network136 and to the transponder via a USB connector 132.

[0054] Although the point of interaction device is described herein withrespect to a merchant point of sale (POS) device, the invention is notto be so limited. Indeed, a merchant POS device is used herein by way ofexample, and the point of interaction device may be any device capableof receiving fob account data. In this regard, the POS may be any pointof interaction device enabling the user to complete a transaction usingfob 102. POS device 110 may be in further communication with a customerinterface 118 (via data link 128) for entering at least a customeridentity verification information. In addition, POS device 110 may be incommunication with a merchant host network 112 (via data link 124) forprocessing any transaction request. In this arrangement, informationprovided by RFID reader 104 is provided to POS device 110 of merchantsystem 130 via data link 122. POS device 110 may receive the information(and alternatively may receive any identity verifying information fromcustomer interface 118 via data link 128) and provide the information tohost system 112 for processing.

[0055] A variety of conventional communications media and protocols maybe used for data links 120, 122, 124, and 128. For example, data links120, 122, 124, and 128 may be an Internet Service Provider (ISP)configured to facilitate communications over a local loop as istypically used in connection with standard modem communication, cablemodem, dish networks, ISDN, Digital Subscriber Lines (DSL), or anywireless communication media. In addition, merchant system 130 includingPOS device 110 and host network 112 may reside on a local area networkwhich interfaces to a remote network (not shown) for remoteauthorization of an intended transaction. Merchant system 130 maycommunicate with the remote network via a leased line, such as a T1, D3line, or the like. Such communications lines are described in a varietyof texts, such as, “Understanding Data Communications,” by Gilbert Held,which is incorporated herein by reference.

[0056] An account number, as used herein, may include any identifier foran account (e.g., credit, charge debit, checking, savings, reward,loyalty, or the like) which may be maintained by a transaction accountprovider (e.g., payment authorization center) and which may be used tocomplete a financial transaction. A typical account number (e.g.,account data) may be correlated to a credit or debit account, loyaltyaccount, or rewards account maintained and serviced by such entities asAmerican Express®, Visa® and/or MasterCard® or the like. For ease inunderstanding, the present invention may be described with respect to acredit account. However, it should be noted that the invention is not solimited and other accounts permitting an exchange of goods and servicesfor an account data value is contemplated to be within the scope of thepresent invention.

[0057] In addition, the account number (e.g., account data) may beassociated with any device, code, or other identifier/indicia suitablyconfigured to allow the consumer to interact or communicate with thesystem, such as, for example, authorization/access code, personalidentification number (PIN), Internet code, digital certificate,biometric data, and/or other identification indicia. The account numbermay be optionally located on a rewards card, charge card, credit card,debit card, prepaid card, telephone card, smart card, magnetic stripecard, bar code card, and/or the like. The account number may bedistributed and stored in any form of plastic, electronic, magnetic,and/or optical device capable of transmitting or downloading data to asecond device. A customer account number may be, for example, asixteen-digit credit card number, although each credit provider has itsown numbering system, such as the fifteen-digit numbering system used byAmerican Express®. Each company's credit card numbers comply with thatcompany's standardized format such that the company using asixteen-digit format will generally use four spaced sets of numbers, asrepresented by the number “0000 0000 0000 0000”. In a typical example,the first five to seven digits are reserved for processing purposes andidentify the issuing bank, card type and, etc. In this example, the lastsixteenth digit is used as a sum check for the sixteen-digit number. Theintermediary eight-to-ten digits are used to uniquely identify thecustomer. The account number stored as Track 1 and Track 2 data asdefined in ISO/IEC 7813, and further may be made unique to fob 102. Inone exemplary embodiment, the account number may include a unique fobserial number and user identification number, as well as specificapplication applets. The account number may be stored in fob 102 insidea database 214, as described more fully below. Database 214 may beconfigured to store multiple account numbers issued to fob 102 user bythe same or different account providing institutions. Where the accountdata corresponds to a loyalty or rewards account, database 214 may beconfigured to store the attendant loyalty or rewards points data.

[0058]FIG. 2 illustrates a block diagram of the many functional blocksof an exemplary fob 102 in accordance with the present invention. Fob102 may be a RFID fob 102 which may be presented by the user tofacilitate an exchange of funds or points, etc., for receipt of goods orservices. As described herein, by way of example, fob 102 may be a RFIDfob which may be presented for facilitating payment for goods and/orservices.

[0059] Fob 102 may include an antenna 202 for receiving an interrogationsignal from RFID reader 104 via antenna 106 (or alternatively, viaexternal antenna 108). Fob antenna 202 may be in communication with atransponder 114. In one exemplary embodiment, transponder 114 may be a13.56 MHz transponder compliant with the ISO/IEC 14443 standard, andantenna 202 may be of the 13 MHz variety. Transponder 114 may be incommunication with a transponder compatible modulator/demodulator 206configured to receive the signal from transponder 114 and configured tomodulate the signal into a format readable by any later connectedcircuitry. Further, modulator/demodulator 206 may be configured toformat (e.g., demodulate) a signal received from the later connectedcircuitry in a format compatible with transponder 114 for transmittingto RFID reader 104 via antenna 202. For example, where transponder 114is of the 13.56 MHz variety, modulator/demodulator 206 may be ISO/IEC14443-2 compliant.

[0060] Modulator/demodulator 206 may be coupled to a protocol/sequencecontroller 208 for facilitating control of the authentication of thesignal provided by RFID reader 104, and for facilitating control of thesending of fob 102 account number. In this regard, protocol/sequencecontroller 208 may be any suitable digital or logic driven circuitrycapable of facilitating determination of the sequence of operation forfob 102 inner-circuitry. For example, protocol/sequence controller 208may be configured to determine whether the signal provided by RFIDreader 104 is authenticated, and thereby providing to RFID reader 104the account number stored on fob 102.

[0061] Protocol/sequence controller 208 may be further in communicationwith authentication circuitry 210 for facilitating authentication of thesignal provided by RFID reader 104. Authentication circuitry may befurther in communication with a non-volatile secure memory database 212.Secure memory database 212 may be any suitable elementary file systemsuch as that defined by ISO/IEC 7816-4 or any other elementary filesystem allowing a lookup of data to be interpreted by the application onthe chip. Database 212 may be any type of database, such as relational,hierarchical, object-oriented, and/or the like. Common database productsthat may be used to implement the databases include DB2 by IBM (WhitePlains, N.Y.), any of the database products available from OracleCorporation (Redwood Shores, Calif.), Microsoft Access or MSSQL byMicrosoft Corporation (Redmond, Wash.), or any other database product.Database 212 may be organized in any suitable manner, including as datatables or lookup tables. Association of certain data may be accomplishedthrough any data association technique known and practiced in the art.For example, the association may be accomplished either manually orautomatically. Automatic association techniques may include, forexample, a database search, a database merge, GREP, AGREP, SQL, and/orthe like. The association step may be accomplished by a database mergefunction, for example, using a “key field” in each of the manufacturerand retailer data tables. A “key field” partitions the databaseaccording to the high-level class of objects defined by the key field.For example, a certain class may be designated as a key field in boththe first data table and the second data table, and the two data tablesmay then be merged on the basis of the class data in the key field. Inthis embodiment, the data corresponding to the key field in each of themerged data tables is preferably the same. However, data tables havingsimilar, though not identical, data in the key fields may also be mergedby using AGREP, for example.

[0062] The data may be used by protocol/sequence controller 208 for dataanalysis and used for management and control purposes, as well assecurity purposes. Authentication circuitry may authenticate the signalprovided by RFID reader 104 by association of the RFID signal toauthentication keys stored on database 212. Encryption circuitry may usekeys stored on database 212 to perform encryption and/or decryption ofsignals sent to or from RFID reader 104.

[0063] In addition, protocol/sequence controller 208 may be incommunication with a database 214 for storing at least fob 102 accountdata, and a unique fob 102 identification code. Protocol/sequencecontroller 208 may be configured to retrieve the account number fromdatabase 214 as desired. Database 214 may be of the same configurationas database 212 described above. The fob account data and/or unique fobidentification code stored on database 214 may be encrypted prior tostorage. Thus, where protocol/sequence controller 208 retrieves theaccount data, and or unique fob identification code from database 214,the account number may be encrypted when being provided to RFID reader104. Further, the data stored on database 214 may include, for example,an unencrypted unique fob 102 identification code, a useridentification, Track 1 and 2 data, as well as specific applicationapplets.

[0064] Fob 102 may be configured to respond to multiple interrogationfrequency transmissions provided by RFID reader 104. That is, asdescribed more fully below, RFID reader 104 may provide more than one RFinterrogation signal. In this case, fob 102 may be configured to respondto the multiple frequencies by including in fob 102 one or moreadditional RF signal receiving/transmitting units 226. RF signalreceiving/transmitting unit 226 may include an antenna 218 andtransponder 220 where antenna 218 and transponder 220 are compatiblewith at least one of the additional RF signals provided by RFID reader104. For example, in one exemplary embodiment, fob 102 may include a 134KHz antenna 218 configured to communicate with a 134 KHz transponder220. In this exemplary configuration, an ISO/IEC 14443-2 compliantmodulator/demodulator may not be required. Instead, the 134 KHztransponder may be configured to communicate directly withprotocol/sequence controller 208 for transmission and receipt ofauthentication and account number signals as described above.

[0065] In another embodiment, fob 102 may further include a universalserial bus (USB) connector 132 for interfacing fob 102 to a userinterface 134. User interface 134 may be further in communication withPOS device 110 via network 136. Network 136 may be the Internet, anintranet, or the like as is described above with respect to network 112.Further, user interface 134 may be similar in construction to anyconventional input devices and/or computing systems aforementioned forpermitting the system user to interact with the system. In one exemplaryembodiment, fob 102 may be configured to facilitate online Internetpayments. A USB converter 222 may be in communication with a USBconnector 232 for facilitating the transfer of information between themodulator/demodulator 206 and USB connector 132. Alternatively, USBconverter 222 may be in communication with protocol/sequence controller208 to facilitate the transfer of information between protocol/sequencecontroller 208 and USB connector 132.

[0066] Where fob 102 includes a USB connector 132, fob 102 may be incommunication with, for example, a USB port on user interface 134. Theinformation retrieved from fob 102 may be compatible with credit cardand/or smart card technology enabling usage of interactive applicationson the Internet. No RFID reader may be required in this embodiment sincethe connection to POS device 110 may be made using a USB port on userinterface 134 and network 136.

[0067] Fob 102 may include means for enabling activation of the fob bythe user. In one exemplary embodiment, a switch 230 which may beoperated by the user of fob 102. Switch 230 on fob 102 may be used toselectively or inclusively activate fob 102 for particular uses. In thiscontext, the term “selectively” may mean that switch 230 enables theuser to place fob 102 in a particular operational mode. For example, theuser may place fob 102 in a mode for enabling purchase of a good or of aservice using a selected account number. Alternatively, the fob may beplaced in a mode as such that the fob account number is provided by USBport 132 (or serial port) only and the fob transponder 114 is disabled.In addition, the term “inclusively” may mean that fob 102 is placed inan operational mode permitting fob 102 to be responsive to the RFinterrogation and interrogation via USB connector 132. In one particularembodiment, switch 230 may remain in an OFF position ensuring that oneor more applications or accounts associated with fob 102 arenon-reactive to any commands issued by RFID reader 104. As used herein,the OFF position may be termed the “normal” position of activationswitch 230, although other normal positions are contemplated.

[0068] In another exemplary embodiment, when switch 230 is moved fromthe OFF position, fob 102 may be deemed activated by the user. That is,switch 230 may activate internal circuitry in fob 102 for permitting thefob to be responsive to RF signals (e.g., commands from RFID reader104). In this way, switch 230 may facilitate control of the active andinactive states of fob 102. Such control increases the system securityby preventing inadvertent or illegal use of fob 102.

[0069] In one exemplary embodiment, switch 230 may be a simplemechanical device in communication with circuitry which may electricallyprevent the fob from being powered by a RFID reader. That is, whenswitch 230 is in its normal position, switch 230 may provide a short tofob 102 internal circuitry, preventing fob 102 from being responsive tointerrogation by RF or via the USB connector 230. In this arrangement,switch 230 may be, for example, a “normally closed” (NC) configuredswitch, which may be electrically connected to the antenna 202 at theinterface of the antenna 202 and transponder 114. Switch 230 may bedepressed, which may open switch 230 fully activating the antenna 202.

[0070] In yet another exemplary embodiment, fob 102 may include abiometric sensor and biometric membrane configured to operate as switch230 and activate fob 102 when provided biometric signal from fob 102user. Such biometric signal may be the digital reading of a fingerprint,thumbprint, or the like. Typically, where biometric circuitry is used,the biometric circuitry may be powered by an internal voltage source(e.g., battery). In this case, the switch may not be a simple mechanicaldevice, but a switch which is powered. In yet another exemplaryembodiment, switch 230 may be battery powered though no biometriccircuitry is present in fob 102.

[0071] In yet another embodiment, switch 230 may be a logic switch.Where switch 230 is a logic switch, switch 230 control software may beread from the sequence controller 208 to selectively control theactivation of the various fob 102 components.

[0072]FIG. 3 illustrates an exemplary block diagram of RFID reader 104in accordance with an exemplary embodiment of the present invention.RFID reader 104 includes, for example, an antenna 106 coupled to a RFmodule 302, which is further coupled to a control module 304. Inaddition, RFID reader 104 may include an antenna 108 positioned remotelyfrom RFID reader 104 and coupled to RFID reader 104 via a suitable cable120, or other wire or wireless connection.

[0073] RF module 302 and antenna 106 may be suitably configured tofacilitate communication with fob 102. Where fob 102 is formatted toreceive a signal at a particular RF frequency, RF module 302 may beconfigured to provide an interrogation signal at that same frequency.For example, in one exemplary embodiment, fob 102 may be configured torespond to an interrogation signal of about 13.56 MHz. In this case,RFID antenna 106 may be 13 MHz and may be configured to transmit aninterrogation signal of about 13.56 MHz. That is, fob 102 may beconfigured to include a first and second RF module (e.g., transponder)where the first module may operate using a 134 kHz frequency and thesecond RF module may operate using a 13.56 MHz frequency. RFID reader104 may include two receivers which may operate using the 134 kHzfrequency, the 13.56 MHz frequency or both. When the reader 104 isoperating at 134 kHz frequency, only operation with the 134 kHz moduleon fob 102 may be possible. When the reader 104 is operating at the13.56 MHz frequency, only operation with the 13.56 MHz module on fob 102may be possible. Where the reader 104 supports both a 134 kHz frequencyand a 13.56 MHz RF module, fob 102 may receive both signals from thereader 104. In this case, fob 102 may be configured to prioritizeselection of the one or the other frequency and reject the remainingfrequency. Alternatively, the reader 104 may receive signals at bothfrequencies from the fob upon interrogation. In this case, the reader104 may be configured to prioritize selection of one or the otherfrequency and reject the remaining frequency.

[0074] Further, protocol/sequence controller 314 may include an optionalfeedback function for notifying the user of the status of a particulartransaction. For example, the optional feedback may be in the form of anLED, LED screen and/or other visual display which is configured to lightup or display a static, scrolling, flashing and/or other message and/orsignal to inform fob 102 user that the transaction is initiated (e.g.,fob is being interrogated), the fob is valid (e.g., fob isauthenticated), transaction is being processed, (e.g., fob accountnumber is being read by RFID reader) and/or the transaction is acceptedor denied (e.g., transaction approved or disapproved). Such an optionalfeedback may or may not be accompanied by an audible indicator (or maypresent the audible indicator singly) for informing fob 102 user of thetransaction status. The audible feedback may be a simple tone, multipletones, musical indicator, and/or voice indicator configured to signifywhen the fob 102 is being interrogated, the transaction status, or thelike.

[0075] RFID antenna 106 may be in communication with a transponder 306for transmitting an interrogation signal and receiving at least one ofan authentication request signal and/or an account data from fob 102.Transponder 306 may be of similar description as transponder 114 of FIG.2. In particular, transponder 306 may be configured to send and/orreceive RF signals in a format compatible with antenna 202 in similarmanner as was described with respect to fob transponder 114. Forexample, where transponder 306 is 13.56 MHz RF rated antenna 202 may be13.56 MHz compatible. Similarly, where transponder 306 is ISO/IEC 14443rated, antenna 106 may be ISO/IEC 14443 compatible.

[0076] RF module 302 may include, for example, transponder 306 incommunication with authentication circuitry 308 which may be incommunication with a secure database 310. Authentication circuitry 308and database 310 may be of similar description and operation asdescribed with respect to authentication circuitry 210 and secure memorydatabase 212 of FIG. 2. For example, database 310 may store datacorresponding to fob 102 which are authorized to transact business oversystem 100. Database 310 may additionally store RFID reader 104identifying information for providing to fob 102 for use inauthenticating whether RFID reader 104 is authorized to be provided thefob account number stored on fob database 214.

[0077] Authentication circuitry 308 may be of similar description andoperation as authentication circuitry 210. That is, authenticationcircuitry 308 may be configured to authenticate the signal provided byfob 102 in similar manner that authentication circuitry 210 may beconfigured to authenticate the signal provided by RFID reader 104. As isdescribed more fully below, fob 102 and RFID reader 104 engage in mutualauthentication. In this context, “mutual authentication” may mean thatoperation of the system 100 may not take place until fob 102authenticates the signal from RFID reader 104, and RFID reader 104authenticates the signal from fob 102.

[0078]FIG. 4 is a flowchart of an exemplary authentication process inaccordance with the present invention. The authentication process isdepicted as one-sided. That is, the flowchart depicts the process ofRFID reader 104 authenticating fob 102, although similar steps may befollowed in the instance that fob 102 authenticates RFID reader 104.

[0079] As noted, database 212 may store security keys for encrypting ordecrypting signals received from RFID reader 104. In an exemplaryauthentication process, where RFID reader 104 is authenticating fob 102,RFID reader 104 may provide an interrogation signal to fob 102 (step402). The interrogation signal may include a random code generated bythe RFID reader authentication circuit 210, which is provided to fob 102and which is encrypted using an unique encryption key corresponding tofob 102 unique identification code. For example, protocol/sequencecontroller 314 may provide a command to activate the authenticationcircuitry 308. Authentication circuitry 308 may provide from database310 a fob interrogation signal including a random number as a part ofthe authentication code generated for each authentication signal. Theauthentication code may be an alphanumeric code which is recognizable(e.g., readable) by RFID reader 104 and fob 102. The authentication codemay be provided to fob 102 via the RFID RF interface 306 and antenna 106(or alternatively antenna 108).

[0080] Fob 102 receives the interrogation signal (step 404). Theinterrogation signal including the authorization code may be received atthe RF interface 114 via antenna 202. Once fob 102 is activated, theinterrogation signal including the authorization code may be provided tothe modulator/demodulator circuit 206 where the signal may bedemodulated prior to providing the signal to protocol/sequencecontroller 208. Protocol/sequence controller 208 may recognize theinterrogation signal as a request for authentication of fob 102, andprovide the authentication code to authentication circuit 210. Fob 102may then encrypt the authentication code (step 406). In particular,encryption may be done by authentication circuit 210, which may receivethe authentication code and encrypt the code prior to providing theencrypted authentication code to protocol/sequence controller 208. Fob102 may then provide the encrypted authentication code to RFID reader104 (step 408). That is, the encrypted authentication code may beprovided to RFID reader 104 via modulator/demodulator circuit 206, RFinterface 114 (e.g., transponder 114) and antenna 202.

[0081] RFID reader 104 may then receive the encrypted authenticationcode and decrypt it (step 410). That is, the encrypted authenticationcode may be received at antenna 106 and RF interface 306 and may beprovided to authentication circuit 308. Authentication circuit 308 maybe provided a security authentication key (e.g., transponder systemdecryption key) from database 310. The authentication circuit may usethe authentication key to decrypt (e.g., unlock) the encryptedauthorization code. The authentication key may be provided to theauthentication circuit based on fob 102 unique identification code. Forexample, the encrypted authentication code may be provided along withthe unique fob 102 identification code. The authentication circuit mayreceive fob 102 unique identification code and retrieve from thedatabase 310 a transponder system decryption key correlative to theunique fob 102 identification code for use in decrypting the encryptedauthentication code.

[0082] Once the authentication code is decrypted, the decryptedauthentication code is compared to the authentication code provided byRFID reader 104 at step 402 (step 412) to verify its authenticity. Ifthe decrypted authorization code is not readable (e.g., recognizable) bythe authentication circuit 308, fob 102 is deemed to be unauthorized(e.g., unverified) (step 418) and the operation of system 100 isterminated (step 420). Contrarily, if the decrypted authorization codeis recognizable (e.g., verified) by fob 102, the decrypted authorizationcode is deemed to be authenticated (step 414), and the transaction isallowed to proceed (step 416). In one particular embodiment, theproceeding transaction may mean that fob 102 may authenticate RFIDreader 104 prior to RFID reader 104 authenticating fob 102, although, itshould be apparent that RFID reader 104 may authenticate fob 102 priorto fob 102 authenticating RFID reader 104.

[0083] It should be noted that in an exemplary verification process, theauthorization circuit 308 may determine whether the unlockedauthorization code is identical to the authorization code provided instep 402. If the codes are not identical then fob 102 is not authorizedto access system 100. Although, the verification process is describedwith respect to identicality, identicality is not required. For example,authentication circuit 308 may verify the decrypted code through anyprotocol, steps, or process for determining whether the decrypted codecorresponds to an authorized fob 102.

[0084] Authentication circuitry 308 may additionally be in communicationwith a protocol/sequence controller 314 of similar operation anddescription as protocol/sequence controller 208 of FIG. 2. That is,protocol/sequence device controller 314 may be configured to determinethe order of operation of RFID reader 104 components. For example, FIG.5 illustrates and exemplary decision process under whichprotocol/sequence controller 314 may operate. Protocol/sequencecontroller 314 may command the different components of RFID reader 104based on whether fob 102 is present (step 502). For example, if fob 102is not present, then protocol/sequence controller 314 may command RFIDreader 104 to provide an uninterrupted interrogation signal (step 504).That is, the protocol/sequence controller may command the authenticationcircuit 308 to provide an uninterrupted interrogation signal until thepresence of fob 102 is realized. If fob 102 is present,protocol/sequence controller 314 may command RFID reader 104 toauthenticate fob 102 (step 506).

[0085] As noted above, authentication may mean that protocol/sequencecontroller 314 may command the authentication circuit 308 to provide fob102 with an authorization code. If a response is received from fob 102,protocol/sequence controller may determine if the response is a responseto RFID reader 104 provided authentication code, or if the response is asignal requiring authentication (step 508). If the signal requiresauthentication, then protocol/sequence controller 314 may activate theauthentication circuit as described above (step 506). On the other hand,if fob 102 signal is a response to the provided authentication code,then protocol/sequence controller 314 may command RFID reader 104 toretrieve the appropriate security key for enabling recognition of thesignal (step 510). That is, protocol/sequence controller 314 may commandthe authentication circuit 308 to retrieve from database 310 a securitykey (e.g., transponder system decryption key), unlock the signal, andcompare the signal to the signal provided by RFID reader 104 in theauthentication process (e.g., step 506). If the signal is recognized,protocol/sequence controller 314 may determine that fob 102 isauthorized to access the system 100. If the signal is not recognized,then fob 102 is considered not authorized. In which case,protocol/sequence controller 314 may command the RFID controller tointerrogate for authorized fobs (step 504).

[0086] Once the protocol/sequence controller determines that fob 102 isauthorized, protocol/sequence controller 314 may seek to determine ifadditional signals are being sent by fob 102 (step 514). If noadditional signal is provided by fob 102, then protocol/sequencecontroller 314 may provide all the components of RFID reader 104 toremain idle until such time as a signal is provided (step 516).Contrarily, where an additional fob 102 signal is provided,protocol/sequence controller 314 may determine if fob 102 is requestingaccess to the merchant point of sale terminal 110 (e.g., POS device) orif fob 102 is attempting to interrogate RFID reader 104 for return(e.g., mutual) authorization (step 518). Where fob 102 is requestingaccess to a merchant point of sale terminal 110, protocol/sequencecontroller 314 may command RFID reader 104 to open communications withpoint of sale terminal 110 (step 524). In particular, protocol/sequencecontroller 314 may command the point of sale terminal communicationsinterface 312 to become active, permitting transfer of data between RFIDreader 104 and the merchant point of sale terminal 110.

[0087] On the other hand, if the protocol/sequence controller determinesthat fob 102 signal is a mutual interrogation signal, then theprotocol/sequence controller may command RFID reader 104 to encrypt thesignal (step 520). Protocol/sequence controller 314 may command theencryption authentication circuit 318 to retrieve from database 320 theappropriate encryption key in response to fob 102 mutual interrogationsignal. Protocol/sequence controller 314 may then command RFID reader104 to provide the encrypted mutual interrogation signal to fob 102.Protocol/sequence controller 314 may command the authentication circuit318 to provide an encrypted mutual interrogation signal for fob 102 tomutually authenticate. Fob 102 may then receive the encrypted mutualinterrogation signal and retrieve from authentication circuitry 212 aRFID reader decryption key.

[0088] Although an exemplary decision process of protocol/sequencecontroller 314 is described, it should be understood that a similardecision process may be undertaken by protocol/sequence controller 208in controlling the components of fob 102. Indeed, as described above,protocol/sequence controller 314 may have similar operation and designas protocol/sequence controller 208. In addition, to the above,protocol/sequence controllers 208 and 314 may incorporate in thedecision process appropriate commands for enabling USB interfaces 222and 316, when the corresponding device is so connected.

[0089] Encryption/decryption component 318 may be further incommunication with a secure account number database 320 which stores thesecurity keys necessary for decrypting the encrypted fob account number.Upon appropriate request from protocol/sequence controller 314,encryption/decryption component (e.g., circuitry 318) may retrieve theappropriate security key, decrypt the fob account number and forward thedecrypted account number to protocol sequence controller 314 in anyformat readable by any later connected POS device 110. In one exemplaryembodiment, the account number may be forwarded in a conventionalmagnetic stripe format compatible with the ISO/IEC 7813 standard. Thatis, in accordance with the invention, there is no need to translate orcorrelate the account number to traditional magnetic stripe format as isdone with the prior art. The invention processes the transaction requestdirectly, as if the card associated with the account has been presentedfor payment.

[0090] Upon receiving the account number in magnetic stripe format,protocol/sequence controller 314 may forward the account number to POSdevice 110 via a communications interface 312 and data link 122, as bestshown in FIG. 1. POS device 110 may receive the decrypted account numberand forward the magnetic stripe formatted account number to a merchantnetwork 112 for processing under the merchant's business as usualstandard. In this way, the present invention eliminates the need of athird-party server. Further, where POS device 110 receives a responsefrom network 112 (e.g., transaction authorized or denied),protocol/sequence controller 314 may provide the network response to theRF module 302 for optically and/or audibly communicating the response tofob 102 user.

[0091] RFID reader 104 may additionally include a USB interface 316, incommunication with the protocol/sequence controller 314. In oneembodiment, the USB interface may be a RS22 serial data interface.Alternatively, RFID reader 104 may include a serial interface such as,for example, a RS232 interface in communication with theprotocol/sequence controller 314. The USB connector 316 may be incommunication with a personalization system 116 (shown in FIG. 1B) forinitializing RFID reader 104 to system 100 application parameters. Thatis, prior to operation of system 100, RFID reader 104 may be incommunication with personalization system 116 for populating database310 with a listing of security keys belonging to authorized fobs 102,and for populating database 320 with the security keys to decrypt fob102 account numbers placing the account numbers in ISO/IEC 7813 format.In this way, RFID reader 104 may be populated with a unique identifier(e.g., serial number) which may be used by fob authentication circuitry210 to determine if RFID reader 104 is authorized to receive fob 102encrypted account number.

[0092]FIG. 1B illustrates an exemplary personalization system 100B, inaccordance with the present invention. In general, typicalpersonalization system 100B may be any system for initializing RFIDreader 104 and fob 102 for use in system 100A. With reference to FIG.1B, the similar personalization process for fob 102 may be illustrated.For example, personalization system 116 may be in communication with fob102 via RF ISO 14443 interface 114 for populating fob database 212 withthe security keys for facilitating authentication of the unique RFIDreader 104 identifier. In addition, personalization system 116 maypopulate on database 212 a unique fob 102 identifier for use by RFIDreader 104 in determining whether fob 102 is authorized to access system100. Personalization system 116 may populate (e.g., inject) theencrypted fob 102 account number into fob database 214 for laterproviding to an authenticated RFID reader 104.

[0093] In one exemplary embodiment, personalization system 116 mayinclude any standard computing system as described above. For example,personalization system 116 may include a standard personal computercontaining a hardware security module operable using any conventionalgraphic user interface. Prior to populating the security key informationaccount number and unique identifying information into fob 102 or RFIDreader 104, the hardware security module may authenticate fob 102 andRFID reader 104 to verify that the components are authorized to receivethe secure information.

[0094] FIGS. 6A-B illustrate an exemplary flowchart of a personalizationprocedure which may be used to personalize fob 102 and/or RFID reader104. Although the following description discusses mainly personalizationof fob 102, RFID reader 104 may be personalized using a similar process.The personalization process, which occurs between the personalizationsystem 116 and the device to be personalized (e.g., fob 102 or RFIDreader 104), may begin, for example at step 602. Mutual authenticationmay occur between the personalization system 116 and the device to beauthenticated in much the same manner as was described above with regardto fob 102 mutually authenticating with RFID reader 104. That is,personalization system 116 may transmit a personalization system 116identifier to the device to be authenticated which is compared by thedevice authentication circuitry 210, 308 against personalization systemidentifiers stored in the device database 212, 310. Where a match doesnot occur (step 604), the personalization process may be aborted (step612). Where a match occurs (step 604), the personalization system mayprepare a personalization file to be provided to the device to bepersonalized (step 606). If the personalization system is operatedmanually, the personalization file may be entered into thepersonalization system 116 using any suitable system interface such as,for example, a keyboard (step 606). Where the personalization system 116operator elects to delay the preparation of the personalization files,the system 116 may abort the personalization process (step 610). In thiscontext, the personalization file may include the unique fob 102 or RFIDreader 104 identifier, security key for loading into database 212 and310, and/or security keys for decrypting a fob account number which maybe loaded in database 320.

[0095] Fob 102 may be personalized by direct connection to thepersonalization system 116 via RF ISO/IEC 14443 interface 114, or fob102 may be personalized using RFID reader 104. Personalization system116 and RFID reader 104 may engage in mutual authentication and RFIDreader 104 may be configured to transmit the fob personalization file tofob 102 via RF. Once fob 102 is presented to RFID reader 104 (steps 608,614) for personalization, fob 102 and RFID reader 104 may engage inmutual authentication (step 614). Where fob 102 is not presented to RFIDreader 104 for personalization, the personalization process may beaborted (step 610).

[0096] If fob 102 is detected, the personalization system 116 may createas a part of the personalization file, a unique identifier for providingto fob 102 (step 616). The identifier is unique in that one identifiermay be given only to a single fob. That is, no other fob may have thatsame identifier. The fob may then be configured and loaded with thatidentifier (step 618).

[0097] The encrypted fob 102 account number may be populated into fob102 in the same manner as is described with respect to fob 102 uniqueidentifier. That is, personalization system 116 may pre-encrypt theaccount data (step 620) and inject the encrypted account into fobdatabase 214 (step 622). The encrypted account data may be loaded (e.g.,injected) into fob 102 using RFID reader 104 as discussed above.

[0098] Once the personalization file is populated into fob 102, thepopulated information is irreversibly locked to prevent alteration,unauthorized reading and/or unauthorized access (step 624).Personalization system 116 may then create a log of the personalizationfile information for later access and analysis by the personalizationsystem 116 user (step 626).

[0099] It should be noted that in the event the personalization processis compromised or interrupted (step 628), personalization system 116 maysend a security alert to the user (step 630) and the personalizationprocess may be aborted (step 612). On the other hand, where no suchcompromising or interruption exists, personalization system 116 may beprepared to begin initialization on a second device to be personalized(step 632).

[0100] FIGS. 7A-B illustrate another exemplary embodiment of apersonalization process which may be used to personalize RFID reader104. RFID reader 104 may be in communication with a personalizationsystem 116 via RFID reader USB connection 316 (step 702). Onceconnected, personalization system 116 may establish communications withRFID reader 104 and RFID reader 104 may provide personalization system116 any RFID reader 104 identification data presently stored on RFIDreader 104 (step 704). In accordance with step 708, where RFID reader104 is being personalized for the first time (step 706) RFID reader 104and personalization system 116 may engage in mutual authentication asdescribed above with respect to FIGS. 6A-B. After the mutualauthentication is complete, personalization system 116 may verify thatRFID reader 104 is properly manufactured or configured to operate withinsystem 100. The verification may include evaluating the operation ofRFID reader 104 by determining if the RFID reader will acceptpredetermined default settings. That is, personalization system 116 maythen provide RFID reader 104 a set of default settings (step 708) anddetermine if RFID reader 104 accepts those settings (step 712). If RFIDreader 104 does not accept the default settings, personalization system116 may abort the personalization process (step 714).

[0101] If personalization system 116 determines that the personalizationprocess is not the first personalization process undertaken by RFIDreader 104 (step 706), personalization system 116 and RFID reader 104may engage in a mutual authentication process using the existingsecurity keys already stored on RFID reader 104 (step 710). Ifauthentication is unsuccessful (step 712), personalization system 116may abort the personalization process (step 714).

[0102] Where personalization system 116 and RFID reader 104 successfullymutually authenticate, personalization system 116 may update RFID reader104 security keys (step 716). Updating the security keys may take placeat any time as determined by a system 100 manager. The updating may takeplace as part of a routine maintenance or merely to install currentsecurity key data. The updating may be performed by downloading firmwareinto RFID reader 104 (step 718). In the event that personalizationsystem 116 determines in step 706 that RFID reader 104 is undergoing aninitial personalization, the firmware may be loaded into RFID reader 104for the first time. In this context, “firmware” may include any filewhich enables the RFID reader 102 to operate under system 100guidelines. For example, such guidelines may be directed toward theoperation of RFID reader protocol/sequence controller 314.

[0103] Personalization system 116 may then determine if thepersonalization keys (e.g., security keys, decryption keys, RFIDidentifier) need to be updated or if RFID reader 104 needs to have aninitial installation of the personalization keys (step 720). If so, thenpersonalization system 116 may download the personalization keys asappropriate (step 722).

[0104] Personalization system 116 may then check RFID reader 104 todetermine if fob 102 identifiers and corresponding security keys shouldbe updated or initially loaded (step 724). If no updating is necessarypersonalization system 116 may end the personalization procedure (step732). Contrarily, if personalization system 116 determines that fob 102identifiers and corresponding keys need to be updated or installed,personalization system 116 may download the information onto RFID reader104 (step 726). The information (e.g., fob security keys andidentifiers) may be downloaded in an encrypted format and RFID reader104 may store the information in the RFID reader database 310 asappropriate (step 728). Personalization system 116 may then create orupdate a status log cataloging for later use and analysis bypersonalization system 116 user (step 730). Upon updating the statuslog, the personalization process may be terminated (step 732).

[0105] It should be noted that, in some instances it may be necessary torepersonalize the RFID reader in similar manner as described above. Inthat instance, the personalization process described in FIGS. 7A and 7Bmay be repeated.

[0106]FIG. 8 illustrates an exemplary flow diagram for the operation ofsystem 100A. The operation may be understood with reference to FIG. 1A,which depicts the elements of system 100A which may be used in anexemplary transaction. The process is initiated when a customer desiresto present fob 102 for payment (step 802). Upon presentation of fob 102,the merchant initiates the RF payment procedure via an RFID reader 104(step 804). In particular, the RFID reader sends out an interrogationsignal to scan for the presence of fob 102 (step 806). The RF signal maybe provided via the RFID reader antenna 106 or optionally via externalantenna 108. The customer then may present fob 102 for payment (step808) and fob 102 is activated by the RF interrogation signal provided.

[0107] Fob 102 and RFID reader 104 may then engage in mutualauthentication (step 810). Where the mutual authentication isunsuccessful, an error message may be provided to the customer via theRFID optical and/or audible indicator (step 814) and the transaction maybe aborted (step 816). Where the mutual authentication is successful(step 812), RFID reader 104 may provide the customer with an appropriateoptical and/or audible message (e.g., “transaction processing” or“wait”) (step 818). The fob protocol/sequence controller 208 may thenretrieve from database 214 an encrypted fob account number and providethe encrypted account number to RFID reader 104 (step 820).

[0108] RFID reader 104 may then decrypt the account number and convertthe account number into magnetic stripe (ISO/IEC 7813) format (step 822)and provide the unencrypted account number to merchant system 130 (step828). In particular, the account number may be provided to POS 110device for transmission to merchant network 112 for processing.Exemplary processing methods according to the present invention arediscussed with respect to FIGS. 10-13, shown below. Upon processing, POSdevice 110 may then send an optical and/or audible transaction statusmessage to RFID reader 104 (step 830) for communication to the customer(step 832).

[0109] The methods for processing the transactions may include one ofseveral formats as required by the fob issuer. For example, oneprocessing method may include processing the transaction under apreloaded fob format wherein a payment value (e.g., monetary value,reward points value, barter points value, etc.) may be preloaded into apreloaded value account or data file prior to permitting usage of thefob. In this way, the user may be permitted to set aside a paymentamount for transactions for goods and services using the fob. Duringprocessing of the transaction, approval of the transaction may involvecomparing the transaction amount to the amount stored (or remaining) inthe preloaded value data file. Comparison may be made by a preloadedvalue processing system wherein the preloaded value processing systemmay compare the transaction amount to be processed to the preload valuedata file. Where the transaction amount exceeds the amount stored in thepreloaded value account, the preloaded value processing system may denyauthorization for completion of the transaction, request that the userincrease the value in the data file, request another form of payment tosatisfy all or a portion of the transaction amount, and/or any othermeans to satisfy the associated financial institution of payment. Wherethe transaction amount does not exceed the amount stored in thepreloaded value data file account, the preloaded value processing systemmay provide for authorization of the transaction.

[0110] An exemplary preloaded value processing system 1000 is shown withrespect to FIG. 10. Preloaded value processing system 1000 may includefob 102 including transponder 114, which is in communication with amerchant system 130 via RFID reader 104 or computer interface 134 as isdescribed with respect to FIG. 1A. The merchant system may be incommunication with an issuer system 1010, where issuer system 1010 maybe maintained by any entity (e.g., non-financial or financialinstitution, American Express®, Visa® and/or MasterCard®, etc.) whichpermits fob 102 user to store a preload value amount in a preloadedvalue account (e.g., data file) maintained on an issuer database 1012 ofsimilar construction as database 212. Issuer system 1010 may furtherinclude one or more process servers for processing a fob transaction. Asshown, POS device 110 (included in merchant system 130) may be incommunication with an issuer account server (IAS) 1014 for receiving thefob account information from POS device 110. IAS 1014 may be in furthercommunication with a preloaded value authorization server (PLAS) 1016for processing transactions involving a preloaded value fob. PLAS 1016may be in further communication with issuer database 1012 for retrievingfunds from the preloaded value data file (not shown) which are used forsatisfying the preloaded fob or merchant transaction request. In thisinstance, the preloaded value data file may be included on database 1012as, for example, one or more sub-files.

[0111] As used herein, the term “issuer” or “account provider” may referto any entity facilitating payment of a transaction using a fob, and mayinclude systems permitting payment using at least one of a preloaded andnon-preloaded fob. Typical issuers may be, for example, AmericanExpress®, MasterCard®, Visa, Discover®, and the like. In the preloadedvalue processing context, an exchange value (e.g., money, rewardspoints, barter points, etc.) may be stored in a preloaded value datafile for use in completing a requested transaction. In one embodiment,the exchange value is not be stored on the fob itself. Further, thepreloaded value data file may be debited the amount of the transaction,so the preloaded value account may be replenished. As described morefully below, the preloaded value system platform may be used to complete“direct link” transactions. In which case, the preloaded value accountmay function as a place holder and may store a zero value.

[0112] The preloaded value data file may be any conventional data fileconfiguration for storing a value (e.g., monetary, rewards points,barter points, etc.) which may be exchanged for goods or services. Inthat regard, the preloaded value data file may have any configuration asdetermined or desired by the issuer system 1010.

[0113] In exemplary operation, fob identifying information (e.g.,account number or fob marker) may be provided to POS device 110 insimilar manner as was discussed with respect to FIG. 1A. That is, fob102 may be presented to merchant system 130 via RFID reader 104 or acomputer interface 134, which may provide the fob identifyinginformation in Track 1 or Track 2 format, or any format recognizable byPOS device 110 and/or issuer system 1010. POS device 110 included inmerchant system 130 may receive fob 102 identifying information andprovide fob 102 identifying information along with the transactionidentifying information (e.g., amount, quantity, merchantidentification, etc.) to issuer system 1010 for authorization. Merchantsystem 130 may additionally include a merchant system marker oridentifier for indicating a merchant system identity. Merchant system130 may combine fob 102 identifying information, the merchantidentifying information, and/or the transaction identifying information,into a merchant transaction request for providing to the issuer system1010.

[0114] IAS 1014 may receive the transaction and fob identifyinginformation (or merchant transaction request) and suitably recognizethat the transaction is being requested relative to a preloaded valueaccount associated with a preloaded fob. That is, IAS 1014 may recognizethat the user has presented a preloaded fob 102 for payment. Recognitionof fob 102 as a preloaded fob may mean that the fob identifyinginformation includes a marker or identifier indicating that the fob isassociated with a preloaded value data file. Upon recognition of themarker, IAS 1014 may forward transaction and fob identifying informationto PLAS 1016 for processing. PLAS 1016 may compare the transactionamount to the value stored or remaining in the preloaded value todetermine if authorization should be granted or denied. Where thetransaction amount exceeds the value stored in the preloaded value datafile, PLAS 1016 may forward a transaction denied message to IAS 1014 forproviding to the merchant system 130, or the PLAS may facilitate arequest that the user increase the value in the data file, requestanother form of payment to satisfy all or a portion of the transactionamount, and/or any other means to satisfy the associated financialinstitution of current or future payment. Alternatively, where thetransaction amount is less than or equal to the value stored in thepreload value data file PLAS 1016 may deduct from the preloaded valuedata file the necessary amount for satisfaction of the transaction.

[0115] As noted above, in one exemplary embodiment of the presentinvention, PLAS 1016 may provide a transaction denied message to IAS1014 for various financial security reasons, such as where the amountstored in the preloaded value account is less than required forsatisfying the merchant or fob transaction request. In this instance,where the preloaded value falls below a predetermined minimum level(e.g., minimum depletion level), it may be necessary for the fob user toreload the preloaded value data file. Reloading of the preloaded valueaccount may take place manually (e.g., by the fob user telephonically oronline) or may take place automatically when the value stored in thepreloaded value data file is depleted to a predefined level. Where thereloading is done automatically, reloading may occur under rulesestablished by the fob issuer or owner. For example, reloading may occurat preselected time intervals, when the value stored is below apredetermined amount, until a maximum number of reloads in apredetermined time period has occurred or until a maximum reload amountis reached in a predetermined time period.

[0116] In another exemplary operation, processing system 1000 may beoperated offline. For example, merchant system 130 may be offline withrespect to issuer system 1010. That is, transactions may be approved atmerchant system 130, prior to the transaction identifying informationbeing transferred to the issuer system. Instead, merchant system 130 maybe provided an approval protocol for use in evaluating the merchanttransaction request. For example, the approval protocol may provide fortransaction approval where the transaction is below a certain amount,includes a particular merchant or goods or service, or is requested froma particular location or the like. Once the offline transaction iscompleted, the merchant may seek satisfaction of the transaction at alater time-period by submitting the transaction to the issuerindividually, in batch, or under any submission processing determined bythe merchant.

[0117] For offline transactions, fob 102 may include a counter (notshown) which may track the number of offline transactions. Once apredetermined number of transactions are attempted, the counter may beused to facilitate disenabling fob 102 usage. At which point fob 102user may be required to perform an online transaction whereby thecounter may be reset, again permitting offline usage of the fob. As canbe understood, requiring online usage following a predetermined numberof offline usages may function as an additional security measure.

[0118]FIGS. 11A and 11B depict exemplary preloading and reloadingprocesses which may be performed in accordance with the presentinvention. The preloading and reloading processes may be preformed usingone or more servers (e.g., PLAS 1016) in communication with a fundingsource 1104. Although the processes are demonstrated using a PLAS 1016,it is contemplated that any server configured for establishing andmanaging data files may be used. However, to facilitate furtherunderstanding of the invention, the preloading and reloading aspects ofthe invention are described with reference to PLAS 1016.

[0119] PLAS 1016 may be used to establish on the server or on a database(e.g., database 1012) a preloaded value account (e,g, data file) (1106).The preload value account may be funded or maintained by a fobissuer/account provider which may establish a credit, charge, debit,rewards value account, loyalty account, or the like, in connection witha charge or credit card (e.g., Visa, MasterCard, American Express,Discover, etc.), debit or direct debit authorization (DDA) system.

[0120] The preloaded value account may be established to at least apredetermined minimum preload amount or value (e.g., minimum preloadlevel) as determined by the account provider and/or the fob user orowner. In this context, the predetermined minimum value (e.g., minimumpreload value) required to establish the preloaded value account mayvary with respect to a particular fob user. The preloaded value accountmay be loaded (e.g., preloaded or reloaded) from funds received from oneof a funding source 1104 (American Express, Visa, MasterCard, Discover,fuel cards, or the like). Further, the preloaded value account may beloaded with value received from loyalty or rewards points provider. Tofacilitate the understanding of the invention, the loyalty or rewardspoint provider may be referred to herein as a funding source. Thus, PLAS1016 may communicate with the funding source 1104 to obtain funds orvalue for loading and/or reloading the preloaded value account (1108).

[0121]FIG. 11B shows an exemplary reloading process in accordance withthe invention. During operation, a consumer may present to merchantsystem 130 the prepaid fob 102 for purchasing goods or services (1110).The preloaded value account is then depleted the value amount paid tomerchant system 130. The process for purchasing goods may be repeateduntil the value stored in the preloaded value account equals or is lessthan a minimum level balance (e.g., minimum depletion level). Theminimum depletion level may be predetermined by the fob user or fobissuer, and may be the minimum value permitted to be stored in thepreloaded value account before the file is to be reloaded.

[0122] Once the preloaded value data is depleted such that the minimumdepletion level is reached, PLAS 1016 may trigger an automatic reload toreload the preloaded value account from funds retrieved from the fundingsource 1104 (1112). The amount of funds retrieved may be sufficient forloading the preloaded value account to the minimum amount describedabove or to some other predetermined reload value. In one exemplaryembodiment, PLAS 1016 may trigger automatic reloading where apredetermined minimum depletion level (e.g., “minimum level balance”) isreached. That is, the preloaded value account may not be entirelydepleted to zero value before automatic reloading occurs. In thisinstance, PLAS 1016 may charge the funding necessary for automaticreloading against the available funds at funding source 1104. In anotherexemplary embodiment, the automatic reloading may occur where thetransaction exceeds the amount stored in or remaining in the preloadedvalue account. In this way, the preloaded value account may be restoredto an amount necessary for completion of the transaction. For example,where automatic reloading restores the preloaded value account to avalue suitable for transaction completion, the preloaded value accountmay be automatically reloaded prior to processing the transaction.

[0123] In another exemplary embodiment, automatic reloading may occurbased on different user or issuer automatic reload criteria. Otherautomatic reload criteria may include, but are not limited to, reloadinguntil a defined maximum load amount in a defined time period is reached,reloading at a selected reoccurring time interval (e.g., once a month),reloading as permitted until a defined maximum number of reloads in aspecified time period is reached, or reloading until a defined maximumreload amount is reached in a specified time period. In some instances,reloading may be accomplished manually, such as, for example, when thefob user contacts the issuer telephonically or via user interface toprovide a specified funding criteria and funding source for use inreloading the preloaded value account.

[0124] In yet another exemplary embodiment, the preloaded valuetransaction processing system may permit approval of a transaction wherethe transaction value exceeds the preloaded value amount stored in thepreloaded value account. That is, the preloaded fob may be used forpurchases exceeding the preloaded value amount provided that the chargesubmitted by the merchant is less than or equal to the maximum reloadamount permitted plus the amount stored on the card at the time thecharge is submitted.

[0125] In another exemplary embodiment, the preloaded value system mayapprove transactions based on a particular merchant's transactionprocessing protocol. Where the issuer has reviewed and/or approved amerchant's transaction processing method, the system may take the methodin consideration in determining whether to approve a merchant'stransaction request. For example, a merchant's transaction processingmethod may include the merchant submitting transaction requests whichexceed the preloaded value amount, but the actual charge may be lessthan or equal to the preloaded value amount. Under this transactionprocessing method a merchant, such as, for example, a gasoline merchant,may seek pre-approval of an anticipated gasoline fueling amount. Neitherthe consumer nor the merchant may know the exact final value of thepurchase, especially, for example, where the consumer decides to fillhis automobile gas tank or purchase non-fuel items. Thus, the merchantmay submit a transaction request which may be higher than the finalamount of the transaction. The merchant may submit the transactionrequest in real-time or at a later time period in a similar manner as isdescribed above with respect to offline transaction request processing.In either on line or off line processing, the preloaded valuetransaction processing system may still be configured to approve thetransaction request. The processing system may recognize that atransaction came from a particular merchant and institute apredetermined approval protocol correlative to that merchant, since theapproval protocol may include information that the merchant is sending atransaction request exceeding the actual charge.

[0126] The transaction processing system may use any one of theacceptable techniques for identifying merchants, such as recognition ofthe merchant ID, or a marker appended to the transaction, or the like.The processing system may correlate the merchant ID with a merchantprotocol for requesting a transaction approval of an amount greater thanthe preloaded value (or reload value), and approve the merchant requestaccordingly.

[0127] In accordance with an alternate exemplary embodiment of apreloaded value processing system 1000, upon receiving the transactionrequest from the IAS 1014, PLAS 1016 may evaluate the transactionrequest based upon several risk criteria established by the issuer foreither online or offline transactions. If all the criteria aresuccessfully met, then PLAS 1016 may send authorization of thetransaction (e.g., “transaction granted”) to IAS 1014 for providing tomerchant system 130. Simultaneous with or subsequent to, providing thetransaction authorization to the IAS 1014, PLAS 1016 may seeksatisfaction of the transaction from the fob value account maintained onthe account provider database 1012. The transaction request may beprovided to IAS 1014 for processing. That is, IAS 1014 may seek todeduct the transaction value from the balance of the amount stored inthe preloaded value account.

[0128]FIG. 12 depicts an exemplary embodiment of another transactionprocessing system (“direct link” system) 1200 in accordance with thepresent invention. More particularly, FIG. 12 depicts a direct linksystem 1200 which may be used to process a merchant transaction request.In this context, a direct link system may be any system whichfacilitates satisfaction of a transaction request using a fob or otherpresentable medium (credit card, charge card, debit card, or the like)directly linked to an account which stores an exchange value (e.g.,money, credit or charge, or rewards points, etc.). In this instance, thepreloaded value account may not be preloaded as described above.Further, the preloaded value account may be linked to a contactfinancial product such as a credit, debit, and/or DDA card, and thelike, which may be presented for payment of goods and services. In thisregard, the fob (here called “direct link fob”) and the card areassociated with the same funding source and the user or merchant mayseek satisfaction of a transaction from the funding source independentof whether the direct link fob or card is used. In the exemplary directlink system 1200, the direct link fob 102 user may not establish apreloaded value account with value. Instead, the preloaded value accountmay perpetually store a zero value or fob 102 may be associated with afob transaction account which may be used to provide payment to themerchant for goods and services where the account may be a credit,debit, loyalty account or the like.

[0129] In accordance with an exemplary embodiment of the invention, atransaction request associated with a direct link fob 102 may beprocessed using the preloaded value transaction system processingdescribed above. However, as noted, in this instance the preloaded valueaccount is used as a place holder storing a zero value. A transactionaccount containing a transaction account value which is associated withthe direct link fob is treated as the funding source for satisfyingdirect link transactions. In this instance, the transaction may besatisfied according to a fob user or issuer predefined protocol orcriteria.

[0130] As shown, merchant system 130 may be in communication with anissuer system 1010 for receiving a merchant transaction request. Moreparticularly, POS device 110 may be in communication with an issuerserver, such as, for example, an issuer account server (IAS) 1014 forreceiving the merchant and/or transaction identifying information. IAS1014 may be in further communication with a PLAS 1016 for processing themerchant transaction request. In some instances PLAS 1016 may be infurther communication with a second IAS 1202, although a second IAS 1202may not be required where one or more of the existing servers mayperform the functions of IAS 1202 described below. However, the IAS 1202is included herein to simplify the understanding the operation of thisexemplary embodiment.

[0131] In exemplary operation of system 1200, the direct link fobidentifying information (e.g., fob identifier or account number) may beprovided to POS device 110 in similar manner as was discussed withrespect to FIG. 1A. That is, the direct link fob 102 may be presented tomerchant system 130 via RFID reader 104 or computer interface 134, whichmay provide the direct link fob 102 identifying information in Track 1or Track 2 format. POS device 110 included in merchant system 130 mayreceive the direct link fob 102 identifying information and provide thedirect link fob 102 identifying information along with the transactionidentifying information (e.g., amount, quantity, merchantidentification, etc.) to issuer system 1010 for authorization.

[0132] IAS 1014 may receive the transaction and fob identifyinginformation and recognize that the transaction as being requestedrelative to a direct link fob 102. Recognition of the direct link fob102 in this instance may mean that the direct link fob 102 identifyinginformation includes a marker or identifier indicating that the fob isassociated with a zero value preloaded value account. Upon recognitionof the marker, IAS 1014 may forward the transaction and fob identifyinginformation to PLAS 1016 for processing.

[0133] In similar manner as was described with respect to the operationof the preloaded value processing system of FIG. 10, PLAS 1016 mayevaluate the transaction request based upon several risk criteriaestablished by the issuer. Exemplary risk criteria may include, but arenot limited to, consideration of transaction amount limits for aspecified time period, fob user usage history, fund or reserve limits,pre-determined re-funding rules, user defined limits, or any similarevaluative criteria. If all the criteria are successfully met, then PLAS1016 may send authorization of the transaction (e.g., “transactiongranted”) to IAS 1014 for providing to merchant system 130. Thetransaction authorization may be provided to merchant system 130 basedon evaluation of the risk criteria and not upon the value present inpreloaded value account or direct link transaction account storing valuerelative to the direct link fob.

[0134] After providing the transaction authorization to the IAS 1014,PLAS 1016 may seek authorization of the transaction against the directlink fob account (e.g., transaction account) which is maintained onissuer database 1012, and which is funded by value received from fundingsource 1104. The authorization request may be provided to IAS 1202 forapproval which may retrieve the necessary value from the direct link fobaccount. For example, where the direct link fob account is a charge orcredit account, PLAS 1016 may request authorization from the second IAS1202 and IAS 1202 may assess the transaction amount against the directlink fob account on database 1012. IAS 1202 may seek to record theamount of the transaction in the direct link fob usage history data filefor payment at the end of a billing cycle (e.g., charge account), or theamount may be recorded on the fob direct link fob usage data file forpayment at a date later than the end of the billing cycle (e.g., creditaccount).

[0135] In an alternative operation PLAS 1016 may assess the transactionamount against the direct link fob account, without use of a second IAS1202. Whether the transaction is processed using a second IAS 1202, itis to be understood that value may not be immediately transferred to themerchant system from the direct link fob account for satisfying thetransaction. Instead, the direct link fob issuer may guaranteesatisfaction of the merchant transaction by, for example, request untila certain value is retrieved from the direct link fob account at the endof the billing cycle or later. That is, PLAS 1016 may provideauthorization of the transaction, but may not retrieve the necessaryvalue for satisfying the transaction until after the merchant provides arequest for settlement to the issuer system.

[0136] In yet another exemplary transaction processing system 1300depicted in FIG. 13, merchant system 130 may provide a batch filecontaining multiple fob transaction requests to be processed to aprocess server 1302 where the multiple fob transactions may include bothpreloaded value and direct link transaction request. The system 1300 mayinclude a processserver 1302 which distinguished between preloaded valueand direct link transaction requests. That is, process server 1302 maybe used for separating the fob transactions which are associated with apreloaded fob account and those that are not associated with a preloadedfob account, as discussed more fully below. Process server 1302 mayfurther be in communication with IAS 1014 for seeking settlement of thetransaction. IAS 1014 may process the transaction request in accordancewith the direct link transaction process or the preloaded valuetransaction platform described above.

[0137] In exemplary operation of system 1300, process server 1302 mayreceive the settlement file and identify the files according to thenature of the transaction request. For example, process server 1302 mayplace markers on the files received and create sub-files of transactionrequests relative to the type of fob used in the transaction (e.g.,preloaded fob, and direct link fob associated with a charge or creditaccount). The process server may create the sub-files relative to thefile markers. Process server 1302 may create a first fob transactionfile for merchant payables and a second fob transaction file foraccounts receivable to be forwarded to IAS 1014 for processing. Wherethe sub-file includes merchant payable, process server 1302 may providefunds to the merchant for payment of the transaction, where the fundsprovided may be equivalent to the transaction amount minus discountrevenues. The funds may be retrieved from the funding source forproviding to the merchant. Alternatively, process server 1302 may createa second fob transaction file for accounts receivable payments andforwarded the second fob transaction file to IAS 1014. IAS 1014 may thenprocess the transaction request according to the processes described inFIGS. 10 and 12. That is, IAS 1014 may distinguish the preloaded fobtransaction requests from those associated with the direct link fob andprocess the transactions accordingly.

[0138] Considering the operation of the various transaction processingsystems described above, it can be seen that the transaction processingsystems described may distinguish when a preloaded fob is used, when acard associated with a fob is used, or when an account associated with apreloaded fob is reloaded. In that regard, the present invention may beused to reward points depending on the nature of the fob usage. Thepoints (e.g., loyalty points) may be stored in a points or rewardsaccount maintained on the issuer database (e.g., database 1012). Therewards points may then later be redeemed from the rewards account forexchange for goods and services as desired by the fob user. For moreinformation on loyalty systems and transaction systems, see, forexample, U.S. patent application Ser. No. 09/836,213, filed on Apr. 17,2001, by inventors Voltmer, et al., and entitled “System And Method ForNetworked Loyalty Program”; U.S. Continuation-In-Part patent applicationSer. No. 10/027,984, filed on Dec. 20, 2001, by inventors Ariff, et al.,and entitled “System And Method For Networked Loyalty Program”; U.S.Continuation-In-Part patent application Ser. No. 10/010,947, filed onNov. 6, 2001, by inventors Haines, et al., and entitled “System AndMethod For Networked Loyalty Program”; the Shop AMEX™ system asdisclosed in Ser. No. 60/230,190, filed Sep. 5, 2000; the MR asCurrency™ and Loyalty Rewards Systems disclosed in Ser. No. 60/197,296,filed on Apr. 14, 2000, Ser. No. 60/200,492, filed Apr. 28, 2000, andSer. No. 60/201,114, filed May 2, 2000; a stored value card as disclosedin Ser. No. 09/241,188, filed on Feb. 1, 1999; a system for facilitatingtransactions using secondary transaction numbers disclosed in Ser. No.09/800,461, filed on Mar. 7, 2001, and also in related provisionalapplications Ser. No. 60/187,620, filed Mar. 7, 2000, Ser. No.60/200,625, filed Apr. 28, 2000, and Ser. No. 60/213,323, filed May 22,2000, all of which are herein incorporated by reference. Other examplesof online membership reward systems are disclosed in Netcentives, U.S.Pat. No. 5,774,870, issued on Jun. 30, 1998, and U.S. Pat. No.6,009,412, issued on Dec. 29, 1999, both of which are herebyincorporated by reference.

[0139] As noted, in one instance, points may be provided when the fob isused in addition to when the card associated with the fob is used. Forexample, IAS 1014 may recognize that a fob is being used and awardpoints (e.g., loyalty points) to the rewards account assigned to the fobuser or associated with the fob. The loyalty points may be awarded basedon any criteria as determined by the fob issuer. Exemplary rewardingcriteria may include rewarding points for, for example, frequency of fobusage, amount of individual purchase using the fob, the total amount ofpurchases in a given time period, location of merchant, type ofmerchant, or any such criteria for incenting fob usage.

[0140] Where the fob is associated with a preloaded value account suchas that described with respect to FIG. 10, points may be awarded foraccount reloading. That is, IAS 1014 may place award points in therewards account relative to the amount loaded or reloaded as required.Further IAS 1014 may place reward points in the rewards account relativeto usage of the fob at a particular merchant or for a particulartransaction.

[0141] It should be noted that the transaction account associated withfob 102 may include a usage restriction, such as, for example, a perpurchase spending limit, a time of day use, a day of week use, certainmerchant use and/or the like, wherein an additional verification isrequired when using the fob outside of the restriction. The restrictionsmay be personally assigned by fob 102 user, or the account provider. Forexample, in one exemplary embodiment, the account may be establishedsuch that purchases above $X (i.e., the spending limit) must be verifiedby the customer. Such verification may be provided using a suitablepersonal identification number (PIN) which may be recognized by fob 102or a payment authorization center (not shown) as being unique to fob 102holder (e.g., customer) and the correlative fob 102 transaction accountnumber. Where the requested purchase is above the established perpurchase spending limit, the customer may be required to provide, forexample, a PIN, biometric sample and/or similar secondary verificationto complete the transaction. That is, for example, fob 102 may enter theunique PIN in a conventional keypad at merchant system 130 or RFIDreader 104. The PIN may be provided to the authorization center forcomparison with a correlative PIN stored on the issuer system.Alternatively, the PIN may be provided to fob 102 via RFID reader 104.Fob 102 may verify the PIN by comparing the PIN to a correlative PINstored on, for example, secure memory 212.

[0142] Where a verification PIN is used as secondary verification theverification PIN may be checked for accuracy against a corroborating PINwhich correlates to fob 102 transaction account number. Thecorroborating PIN may be stored locally (e.g., on fob 102), or may bestored on a database (1012) at the payment authorization center. Thepayment authorization center database may be any database 1012maintained and operated by fob 102 transaction account provider.

[0143] The verification PIN may be provided to POS device 110 using aconventional merchant (e.g., POS) PIN key pad 118 in communication withPOS device 110 as shown in FIG. 1A, or a RFID keypad in communicationwith RFID reader 104. PIN keypad may be in communication with POS device110 (or alternatively, RFID reader 104) using any conventional data linkdescribed above. Upon receiving the verification PIN, RFID reader 104may seek to match the PIN to the corroborating PIN stored on RFID reader104 at database 310 or 320. Alternatively, the verification PIN may beprovided to a payment authorization center to determine whether the PINmatches the PIN stored on the payment authorization center databasewhich correlates to fob 102 account. If a match is made, the purchasemay no longer be restricted, and the transaction may be allowed to becompleted.

[0144] In an alternate embodiment, verification of purchases exceedingthe established spending limit may involve biometrics circuitry includedin fob 102. FIG. 9 is a schematic block diagram of an exemplary fob 102wherein fob 102 includes a biometric security system 902. Biometricsecurity system 902 may include a biometric sensor 904 for sensing thefingerprint of fob 102 user. Biometric sensor 904 may be incommunication with a sensor interface/driver 906 for receiving thesensor fingerprint and activating the operation of fob 102. Incommunication with biometric sensor 904 and sensor interface 906 may bea battery 903 for providing the necessary power for operation of thebiometric security system components.

[0145] In one exemplary application of fob 102 including biometricsecurity system 902, the customer may place his finger on the biometricsensor to initiate the mutual authentication process between fob 102 andRFID reader 104, or to provide secondary verification of the user'sidentity. The sensor fingerprint may be digitized and compared against adigitized fingerprint stored in a database (e.g., security database 212)included on fob 102. Such comparison step may be controlled byprotocol/sequence controller 208 and may be validated by authenticationcircuit 210. Where such verification is made, the mutual authenticationbetween fob 102 and RFID reader 104 may begin, and the transaction mayproceed accordingly. Alternatively, the comparison may be made with adigitized fingerprint stored on a database maintained by fob 102transaction account provider system (not shown). The digitizedfingerprint may be verified in much the same way as is described abovewith respect to the PIN.

[0146] In one exemplary application of fob 102 including biometricsecurity system 902, system 902 may be used to authorize a purchaseexceeding the established per purchase spending limit. In this case,where the customer's intended purchase exceeds the spending limit, thecustomer may be asked to provide assurance that the purchase isauthorized. Accordingly, the customer may provide such verification byplacing his finger over biometric sensor 904. Biometric sensor 904 maythen digitize the fingerprint and provide the digitized fingerprint forverification as described above. Once verified, fob 102 may provide atransaction authorized signal to RF transponder 202 (or alternatively totransponder 220) for forwarding to RFID reader 104. RFID reader 104 maythen provide the transaction authorized signal to POS device 110 insimilar manner as is done with conventional PIN driven systems and POSdevice 110 may process the transaction under the merchant's business asusual standard.

[0147] Additional methods and systems for biometric security for system100 will be discussed further herein.

[0148] In accordance with another exemplary embodiment of the invention,the fob user is provided limited access to a fob user data filemaintained on an issuer system for managing the fob usage and fob userinformation. User may have access over the phone, online, or offline.The fob user may access the fob user data file to change, for example,demographic information (e.g., fob user address, phone number, emailaddress, or the like), the funding source (e.g., credit account, chargeaccount, rewards account, barter account, etc.) associated with the fob,view the transaction history, etc. In addition, the fob user may bepermitted to load or reload the account or alter automatic reloadparameters (e.g., amount to reload, period for reloading, etc.). Wheremore than one fob 102 is correlated to a transaction account, the usermay be provided similar access to the data files corresponding to theadditional fobs.

[0149] With reference to FIG. 1A, the fob user may connect fob 102 tocomputer interface 134 via the USB interface 132. The fob user may thenuse computer interface 134 to access the fob user data file via network136. In particular, network 136 may be in communication with an issuersystem (e.g., system 1010 of FIG. 10) and may be provided limited accessto an issuer server (e.g., server 1014) for managing the fob. Issuerserver 1014 may be in communication with an issuer system database(e.g., 1012) which stores the information to be managed relative to theuser fob user data file. The changes made to the fob user data file bythe fob user may be made in real-time, after a brief delay, or after anextended delay. In one instance, changes may be stored in a batchchanges file on the issuer database for later batch processing.

[0150] In another exemplary embodiment of the present invention, system100 may be configured with one or more biometric scanners, processorsand/or systems. A biometric system may include one or more technologies,or any portion thereof, such as, for example, recognition of abiometric. As used herein, a biometric may include a user's voice,fingerprint, facial, ear, signature, vascular patterns, DNA sampling,hand geometry, sound, olfactory, keystroke/typing, iris, retinal or anyother biometric relating to recognition based upon any body part,function, system, attribute and/or other characteristic, or any portionthereof. Certain of these technologies will be described in greaterdetail herein. Moreover, while some of the examples discussed herein mayinclude a particular biometric system or sample, the inventioncontemplates any of the biometrics discussed herein in any of theembodiments.

[0151] The biometric system may be configured as a security system andmay include a registration procedure in which a user of transactioninstrument (e.g., fob 102) proffers a sample of his fingerprints, DNA,retinal scan, voice, and/or other biometric sample to an authorizedsample receiver (ASR). An ASR may include a local database, a remotedatabase, a portable storage device, a host system, an issuer system, amerchant system, a fob issuer system, an employer, a financialinstitution, a non-financial institution, a loyalty point provider, acompany, the military, the government, a school, a travel entity, atransportation authority, a security company, and/or any other system orentity that is authorized to receive and store biometric samples andassociate the samples with specific biometric databases and/ortransaction instruments (e.g., fobs 102). As used herein, a user of afob, fob user, or any similar phrase may include the person or deviceholding or in possession of the fob, or it may include any person ordevice that accompanies or authorizes the fob owner to use the fob.

[0152]FIG. 14 illustrates an exemplary registration procedure inaccordance with the present invention. In one embodiment, a fob user maycontact an ASR to submit one or more biometric samples to an ASR (step1401). The fob user may contact the ASR and submit a sample in person,through a computer and/or Internet, through software and/or hardware,through a third-party biometric authorization entity, through a kioskand/or biometric registration terminal, and/or by any other direct orindirect means, communication device or interface for a person tocontact an ASR.

[0153] A fob user may then proffer a biometric sample to the ASR (step1403). As used herein, a biometric sample may be any one or more of thebiometric samples or technologies, or portion thereof, described hereinor known in the art. By proffering one or more biometric samples, abiometric may be scanned by at least one of a retinal scan, iris scan,fingerprint scan, hand print scan, hand geometry scan, voice print scan,vascular scan, facial and/or ear scan, signature scan, keystroke scan,olfactory scan, auditory emissions scan, DNA scan, and/or any other typeof scan to obtain a biometric sample. Upon scanning the sample, thesystem may submit the scanned sample to the ASR in portions during thescan, upon completing the scan or in batch mode after a certain timeperiod. The scanned sample may include a hardcopy (e.g., photograph),digital representation, an analog version or any other configuration fortransmitting the sample. The ASR receives the sample and the ASR mayalso receive copies of a fob user's biometric data along with the sampleor at a different time (or within a different data packet) fromreceiving the sample.

[0154] The ASR and/or fob user 102 may correlate and/or register thesample with fob user information to create a data packet for the sampleand store the data packet in digital and/or any storage medium known inthe art. As used herein, a data packet may include the digitizedinformation relating to at least one of a biometric sample, a registeredbiometric sample, a stored biometric sample, a proffered biometric, aproffered biometric sample, user information, transponder information,and/or any other information. The terms “data packet,” “biometricsample,” and “sample” may be used interchangeably. As used herein,registered samples may include samples that have been proffered, storedand associated with user information. By storing the data packet indigital format, the ASR may digitize any information contained in one ofthe biometric scans described herein. By storing the data packet in anystorage medium, the ASR may print and/or store any biometric sample.Hardcopy storage may be desirable for back-up and archival purposes.

[0155] The biometric sample may also be associated with user informationto create a data packet (step 1405). The sample may be associated withuser information at any step in the process such as, for example, priorto submission, during submission and/or after submission. In oneembodiment, the user may input a PIN number or zip code into the POSterminal, then scan the biometric to create the biometric sample. Thelocal POS system may associate the biometric sample data with the PINand zip code, then transmit the entire packet of information to the ASR.In another embodiment, the POS may facilitate transmitting the sample toan ASR, and during the transmission, the sample may be transmittedthrough a third system which adds personal information to the sample.

[0156] The information associated with the biometric sample may includeany information such as, for example, fob user information, fob 102information, fob 102 identifier information, fob 102 vender information,fob 102 operability information, and/or fob 102 manufacturinginformation. Fob 102 information is not limited to transponderinformation and may include information related to any transactioninstrument such as smart cards, credit cards, debit cards,merchant-specific cards, loyalty point cards, cash accounts and anyother transaction instruments and/or accounts. The fob user informationmay also contain information about the user including personalinformation-such as name, address, and contact details; financialinformation—such as one or more financial accounts associated with thefob user; loyalty point information—such as one or more loyalty pointaccounts (e.g., airline miles, charge card loyalty points, frequentdiner points) associated with the fob user; and/or non-financialinformation-such as employee information, employer information, medicalinformation, family information, and/or other information that may beused in accordance with a fob user.

[0157] For example, fob user may have previously associated a creditcard account, a debit card account, and a frequent flier account withhis biometric sample which is stored at an ASR. Later, when fob userdesires to purchase groceries, fob user may submit his biometric samplewhile using fob 102 for the purchase at a POS. The POS may facilitatesending the biometric sample to the ASR such that the ASR authorizes thebiometric sample and checks a look-up table in the ASR database todetermine if any information is associated with the sample. Ifinformation (e.g., financial accounts) is associated with the sample,the ASR may transmit the information to the POS terminal. The POSterminal may then present fob user with a list of the three accountsassociated with the biometric sample. Fob user and/or a merchant maythen chose one of the accounts in order to continue and finalize thetransaction.

[0158] In another embodiment, fob user may associate each account with adifferent biometric sample. For example, during registration, fob usermay submit a sample of his right index fingerprint, and request that thesystem primarily associate this sample with a particular credit cardaccount. Fob user may additionally submit a sample of his left indexfingerprint and request that the system primarily associate the samplewith a particular debit account. Additionally, fob user may submit hisright thumbprint and request that the system primarily associate thatsample with a particular frequent flier account. By “primarily”associating a sample with an account, the system initially associatesthe sample with that account. For example, fob user submitting his rightindex fingerprint for a financial transaction may have money for thetransaction taken from his credit card account. Fob user mayadditionally specify which accounts should be secondarily associatedwith a sample. For example, fob user may have a debit card accountsecondarily associated with his right index fingerprint. As a result, iffob user submits his right index fingerprint for a transaction, and theprimary account associated with the sample is overdrawn or unavailable,the secondary account may be accessed in order to further thetransaction.

[0159] While primary and secondary account association is describedherein, any number of accounts may be associated with a sample.Moreover, any hierarchy or rules may be implemented with respect to theassociation. For example, the fob user may instruct the system to accessa debit card account when it receives a right index fingerprint sample,the purchase qualifies for loyalty points with a certain airline and thepurchase amount is less than $50. The fob user may additionally instructthe system to access a credit card account if it receives a right indexfingerprint sample, the purchase does not qualify for airline miles andthe purchase amount is greater than $50. Further, while fingerprintsamples are discussed herein, any biometric sample may have one or moreaccounts associated with it and may be used to facilitate a transactionusing any of the routines discussed herein.

[0160] The ASR and/or fob user may associate a specific fob 102identifier with the biometric sample by any method known in the art forassociating an identifier (e.g., through the use of software, hardwareand/or manual entry.) The ASR may additionally verify the fob userand/or fob 102 by using one or more forms of the user's secondaryidentification (step 1407). For example, the ASR may verify the fob userby matching the fob information to information retrieved from scanninginformation from a fob user's driver's license. The ASR may verify fob102 by contacting the vendor of fob 102 to confirm that fob 102 wasissued to a specific fob user. In another embodiment, the ASR mayactivate fob 102 during the registration procedure to confirm that thefob 102 transponder identifier and other information is properlyassociated with the fob user and the fob user's specific biometricsamples. The ASR may additionally employ one or more verificationmethods to confirm that the biometric sample belongs to the user, suchas, for example, the ASR may request from the user demographicinformation, further biometric samples and/or any other information. Asused herein, “confirm,” “confirmation” or any similar term includesverifying or substantially verifying the accuracy, existence,non-existence, corroboration, and/or the like of the information,component, or any portion thereof. The ASR may additionally employ oneor more additional processing methods in order to facilitate associationof a biometric sample. As used herein, the term processing may includescanning, detecting, associating, digitizing, printing, comparing,storing, encrypting, decrypting, and/or verifying a biometric and/or abiometric sample, or any portion thereof.

[0161] Upon association, authentication and/or verification of thebiometric sample and fob 102, the system may create a data packet andfor the sample store the data packet and fob 102 identifier (step 1409)in one or more databases on and/or in communication with system 100 viaa network, server, computer, or any other means of communicating asdescribed herein. The database(s) may be any type of database describedherein. For example, a biometric sample stored on fob 102 may be storedin database 212. The database(s) may be located at or operated by any ofthe entities discussed herein such as, for example, the ASR and/or by athird-party biometric database operator.

[0162] The information stored in the database may be sorted or storedaccording to one or more characteristics associated with the sample inorder to facilitate faster access to the stored sample. For example,fingerprint samples may be stored in a separate database than voiceprints. As another example, all fingerprints with certain whirl patternsmay be stored in a separate sub-database and/or database fromfingerprints with arch patterns.

[0163] The biometric samples may also be stored and/or associated with apersonal identification number (PIN) and/or other identifier tofacilitate access to the sample. The PIN may be fob user selected orrandomly assigned to the biometric sample. The PIN may consist of anycharacters such as, for example, alphanumeric characters and/or foreignlanguage characters.

[0164] The system may further protect the samples by providingadditional security with the sample. The security may include, forexample, encryption, decryption, security keys, digital certificates,firewalls and/or any other security methods known in the art anddiscussed herein. One or more security vendors may utilize the securitymethods to store and/or access the biometric samples. The presentinvention anticipates that storage of the biometric samples may be suchthat a sample is first encrypted and/or stored under a securityprocedure, such that the sample may only be accessed by a vendor withthe proper level of access or security which corresponds to or providesaccess to the stored sample. The samples may be accessible by certainvendors such as, for example, fob 102 transaction account providersystem, an issuer system, a merchant system, a fob issuer system, anemployer, a financial institution, a non-financial institution, aloyalty-point provider, a company, the military, the government, aschool, a travel entity, a transportation authority, and/or a securitycompany.

[0165] The fob of the invention may include a particular security systemwherein the security system incorporates a particular biometric system.As shown in FIG. 15, fob 102 includes a biometric security system 1502configured for facilitating biometric security using, for example,fingerprint samples. As used herein, fingerprint samples may includesamples of one or more fingerprints, thumbprints, palmprints,footprints, and/or any portion thereof. Biometric security system 1502may include a biometric sensor 1504 which may be configured with asensor and/or other hardware and/or software for acquiring and/orprocessing the biometric data from the person such as, for example,optical scanning, capacitance scanning, or otherwise sensing the portionof fob user. In one embodiment, biometric sensor 1504 of the securitysystem 1502 may scan a finger of a fob user in order to acquire hisfingerprint characteristics into fob 102. Biometric sensor 1504 may bein communication with a sensor interface/driver 1506 such that sensorinterface 1506 receives the fingerprint information and transmits asignal to controller 208 to facilitate activating the operation of fob102. A power source (e.g., battery 1503) may be in communication withbiometric sensor 1504 and sensor interface 1506 to provide the desiredpower for operation of the biometric security system components.

[0166] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, the user may place his finger on the biometricsensor to initiate the mutual authentication process between fob 102 andRFID reader 104, and/or to provide verification of the user's identity.Fob 102 may digitize the fingerprint and compare it against a digitizedfingerprint stored in a database (e.g., security database 212) includedon fob 102. The fingerprint information may additionally be comparedwith information from one or more third-party databases communicatingwith fob 102 through any communication software and/or hardware,including for example, RFID reader 104, a USB connection, a wirelessconnection, a computer, a network and/or any other means forcommunicating. This transfer of information may include use ofencryption, decryption, security keys, digital certificates and/or othersecurity devices to confirm the security of the sample. Fob 102 mayadditionally communicate with third-party databases to facilitate acomparison between fob 102 identifier and other fob identifiers storedwith the biometric samples. As used herein, compare, comparison andsimilar terms may include determining similarities, differences,existence of elements, non-existence of elements and/or the like.

[0167] Protocol/sequence controller 208 may facilitate the localcomparison to authenticate the biometric and authentication circuit 210may validate the information. Any of the embodiments may alternativelyor additionally include remote comparisons performed or controlled byone or more third-party security vendors. One or more comparisontechniques and/or technologies may be used for comparisons. For example,for fingerprint comparisons, protocol/sequence controller 208 mayutilize an existing database to compare fingerprint minutia such as, forexample, ridge endings, bifurcation, lakes or enclosures, short ridges,dots, spurs and crossovers, pore size and location, Henry Systemcategories such as loops, whorls, and arches, and/or any other methodknown in the art for fingerprint comparisons.

[0168] Fob 102 may additionally be configured with secondary securityprocedures to confirm that fake biometric samples are not being used.For example, to detect the use of fake fingers, fob 102 may be furtherconfigured to measure blood flow, to check for correctly aligned ridgesat the edges of the fingers, and/or any other secondary procedure toreduce biometric security fraud. Other security procedures for ensuringthe authenticity of biometric samples may include monitoring pupildilation for retinal and/or iris scans, pressure sensors, blinkingsensors, human motion sensors, body heat sensors and/or any otherprocedures known in the art for authenticating the authenticity ofbiometric samples.

[0169] After verifying the biometric information, fob 102 and RFIDreader 104 may begin mutual authentication, and the transaction mayproceed accordingly. However, the invention contemplates that theverification of biometric information may occur at any point in thetransaction such as, for example, after the mutual authentication. Atany point in the transaction, the system may additionally request fobuser to enter a PIN and/or other identifier associated with thetransaction account and/or biometric sample to provide furtherverification of fob user's identification. As part of the transaction,fob user payor may be requested to select from one of the financialaccounts, loyalty accounts, credit accounts, debit account, and/or otheraccounts associated with the biometric sample. The user may be presentedwith a list of account options on a display associated with RFID reader104, fob 102, a third-party security device and/or any other financialor transaction device association with a transaction. In anotherembodiment, a payee may select one of the accounts. For example, adepartment store payee may manually and/or automatically select adepartment store issued account, if available, for a transaction.

[0170] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using facialrecognition or recognition of any other body part or object. Asdiscussed herein, facial recognition may include recognition of anyfacial features obtained through a facial scan such as, for example, theeyes, nose, cheeks, jaw line, forehead, chin, ear features, head shape,hairline, neck features, shoulder height and/or any portion thereof.Biometric security system 1502 may include a biometric sensor 1504 whichmay be configured with a video camera, optical scanner, and/or otherhardware and/or software for acquiring the biometric data from theperson such as, for example video scanning, optical scanning orotherwise sensing any portion of fob user. In one embodiment, biometricsensor 1504 of the security system 1502 may scan the face of a fob userin order to acquire his facial characteristics into fob 102. Biometricsensor 1504 may be in communication with a sensor/interface/driver 1506such that sensor 1504 receives the facial information and transmits asignal to controller 208 to facilitate activating the operation of fob102. A power source (e.g., battery 1503) may be in communication withbiometric sensor 1504 and sensor interface 1506 to provide the desiredpower for operation of the biometric security system components.

[0171] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may scan the facial features of thefob user to initiate the mutual authentication process between fob 102and RFID reader 104, and/or to provide verification of the user'sidentity. Security system 1502 may be configured such that fob user maystand at least two-feet away from sensor 1504. Additionally, sensor 1504may be configured to detect facial features of a user turned at least 30degrees toward the camera.

[0172] Fob 102 may digitize the facial scan and compare it against adigitized facial scan stored in a database (e.g., security database 212)included on fob 102. The facial scan information may additionally becompared with information from one or more third-party databasescommunicating with fob 102 through any communication software and/orhardware, including for example, RFID reader 104, a USB connection, awireless connection, a computer, a network and/or any other means forcommunicating. This transfer of information may include use ofencryption, decryption, security keys, digital certificates and/or othersecurity devices to confirm the security of the sample. Fob 102 mayadditionally communicate with third-party databases to facilitate acomparison between fob 102 identifier and other fob identifiers storedwith the biometric samples.

[0173] Protocol/sequence controller 208 may facilitate the localcomparison to authenticate the biometric, and authentication circuit 210may validate the information. Any of the embodiments may alternativelyor additionally include remote comparisons performed or controlled byone or more third-party security vendors. One or more comparisontechniques and/or technologies may be used for comparisons. For example,for facial recognition, protocol/sequence controller 208 may utilize anexisting database to compare nodal points such as the distance betweenthe eyes, the width of the nose, the jaw line, and the depth of theuser's eye sockets. While only some types of nodal points are listed,the present invention recognizes that it is known that there are over 80different nodal points on a human face that may be used for comparisonin the present invention. Additionally, third-party devices such asfacial recognition software and/or hardware systems may be used tofacilitate facial recognition, such as the systems developed by Viisage,Imagis, and Identix which employ complex algorithms that facilitate bothsearching facial and/or ear scans and adjusting stored data based oneyewear, facial hair, and other changes in outward facial and/or earappearance.

[0174] Fob 102 may additionally be configured with secondary securityprocedures to confirm that fake biometric samples are not being used.For example, to detect the use of fake facial features, fob 102 may befurther configured to measure blood flow, to detect a thermal patternassociated with facial features, and/or any other secondary procedure toreduce biometric security fraud. Other security procedures for ensuringthe authenticity of biometric samples may include monitoring pupildilation for retinal and/or iris scans, pressure sensors, blinkingsensors, human motion sensors, body heat sensors and/or any otherprocedures known in the art for authenticating the authenticity ofbiometric samples. After verifying the biometric information, fob 102and RFID reader 104 may begin mutual authentication by any of themethods described herein.

[0175] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using voicerecognition. As discussed herein, voice recognition may includerecognition of voice and/or speaker features such as, phonatedexcitation, whispered excitation, frication excitation, compression,vibration, parametric waveforms, tone, pitch, dialect, annunciation,and/or any portion thereof. As discussed herein, these voice recognitionfeatures may be collectively referred to as a “voice print.” Biometricsecurity system 1502 may include a biometric sensor 1504 which may beconfigured with an audio capture device such as a microphone, telephone,cellular phone, speaker and/or other hardware and/or software foracquiring the biometric data from the person such as, for exampleauditory scanning, recording or otherwise sensing the portion of fobuser.

[0176] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the voice print of the fobuser to initiate the mutual authentication process between fob 102 andRFID reader 104, and/or to provide verification of the user's identity.In one embodiment, biometric sensor 1504 of the security system 1502 maycapture a voice print, when a user recites, for example, a pass phraseor audible PIN. Biometric sensor 1504 may be in communication with asensor/interface/driver 1506 such that sensor 1504 receives the voiceprint and transmits a signal to controller 208 to facilitate activatingthe operation of fob 102. A power source (e.g., battery 1503) may be incommunication with biometric sensor 1504 and sensor interface 1506 toprovide the desired power for operation of the biometric security systemcomponents.

[0177] Fob 102 may digitize the voice print and compare it against adigitized voice print stored in a database (e.g., security database 212)included on fob 102. The voice print information may additionally becompared with information from one or more third-party databasescommunicating with fob 102 through any communication software and/orhardware, including for example, RFID reader 104, a USB connection, awireless connection, a computer, a network and/or any other means forcommunicating. Protocol/sequence controller 208 may facilitate the localcomparison to authenticate the biometric and authentication circuit 210may validate the information. Any of the embodiments may alternativelyor additionally include remote comparisons performed or controlled byone or more third-party security vendors.

[0178] One or more comparison techniques and/or technologies may be usedfor comparisons. For example, for voice recognition, protocol/sequencecontroller 208 may utilize an existing database to compare the voiceprint by comparing voice print waveforms in the time domain, bycomparing energy content in the voice prints across the frequencydomain, by the use of stochastic models and/or template models, and/orby any other voice recognition method known in the art. This transfer ofinformation may include use of encryption, decryption, security keys,digital certificates and/or other security devices to confirm thesecurity of the sample. Fob 102 may additionally communicate withthird-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.Further, the present invention anticipates use of one or morethird-party devices such as voice recognition software and/or hardwaresystems to facilitate voice print comparisons, such as, for exampleSAFLINK and Voice Security Systems.

[0179] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of a recorded voice, system 1502may be further configured to detect audio noise associated with anelectronic device and/or any other secondary procedure to thwartbiometric security fraud. After verifying the biometric information, fob102 and RFID reader 104 may begin mutual authentication by the methodsdescribed herein.

[0180] In another exemplary embodiment of the present invention,biometric security system 1502 may be configured for facilitatingbiometric security using signature recognition. As discussed herein,signature recognition may include recognition of the shape, speed,stroke, stylus pressure, timing information and/or other signatureinformation and/or any portion thereof during the act of signing. Asdiscussed herein, these signature recognition features may becollectively referred to as a “signature scan.” Biometric securitysystem 1502 may include a biometric sensor 1504 which may be configuredwith an LCD screen, digitizing tablet and/or other hardware and/orsoftware that facilitates digitization of biometric data from the personsuch as, for example signature scanning, recording or otherwise sensingthe signature of fob user.

[0181] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the signature scan of thefob user to initiate the mutual authentication process between fob 102and RFID reader 104, and/or to provide verification of the user'sidentity. In one embodiment, biometric sensor 1504 of the securitysystem 1502 may capture a signature scan, when a user signs, forexample, his name or a specified word or phrase. Biometric sensor 1504may be in communication with a sensor/interface/driver 1506 such thatsensor 1504 receives the signature scan and transmits a signal tocontroller 208 to facilitate activating the operation of fob 102. Apower source (e.g., battery 1503) may be in communication with biometricsensor 1504 and sensor interface 1506 to provide the desired power foroperation of the biometric security system components.

[0182] Fob 102 may digitize the signature scan and compare it against adigitized signature scan stored in a database (e.g., security database212) included on fob 102. The signature scan information mayadditionally be compared with information from one or more third-partydatabases communicating with fob 102 through any communication softwareand/or hardware, including for example, RFID reader 104, a USBconnection, a wireless connection, a computer, a network and/or anyother means for communicating. Protocol/sequence controller 208 mayfacilitate the local comparison to authenticate the biometric andauthentication circuit 210 may validate the information. Any of theembodiments may alternatively or additionally include remote comparisonsperformed or controlled by one or more third-party security vendors.

[0183] For example, for voice recognition, protocol/sequence controller208 may utilize an existing database to compare the features of asignature scan by comparing graphs, charts, and or other data relatingto shape, speed, stroke, stylus pressure, timing information and/or byany other signature recognition data. This transfer of information mayinclude use of encryption, decryption, security keys, digitalcertificates and/or other security devices to confirm the security ofthe sample. Fob 102 may additionally communicate with third-partydatabases to facilitate a comparison between fob 102 identifier andother fob identifiers stored with the biometric samples. Further, thepresent invention anticipates use of one or more third-party devicessuch as signature recognition software and/or hardware systems tofacilitate signature scan comparisons, such as, for example CyberSIGN,LCI Computer Group, and Xenetek.

[0184] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of a false signature device, system1502 may be further configured to detect a thermal pattern associatedwith a human hand and/or any other secondary procedure to thwartbiometric security fraud. After verifying the biometric information, fob102 and RFID reader 104 may begin mutual authentication by the methodsdescribed herein.

[0185] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using vascularpattern recognition. As discussed herein, vascular pattern may includerecognition of structures, depths, and other biometric reference pointsof arterial tissues, vein tissues, capillary tissues, epithelialtissues, connective tissues, muscle tissues, nervous and/or other innertissues and/or any portion thereof. As discussed herein, these vascularpattern features may be collectively referred to as a “vascular scan.”Biometric security system 1502 may include a biometric sensor 1504 whichmay be configured with an optical scanner, thermal scanner and/or otherhardware and/or software that facilitates capture of biometric data fromthe person such as, for example scanning, detecting or otherwise sensinga vascular pattern of fob user.

[0186] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the vascular scan of thefob user to initiate the mutual authentication process between fob 102and RFID reader 104, and/or to provide verification of the user'sidentity. In one embodiment, biometric sensor 1504 of the securitysystem 1502 may capture a vascular scan, when a user places his hand infront of an optical scanner. Biometric sensor 1504 may be incommunication with a sensor/interface/driver 1506 such that sensor 1504receives the vascular scan and transmits a signal to controller 208 tofacilitate activating the operation of fob 102. A power source (e.g.,battery 1503) may be in communication with biometric sensor 1504 andsensor interface 1506 to provide the desired power for operation of thebiometric security system components.

[0187] Fob 102 may digitize the vascular scan based on biometricreference points and compare it against a digitized vascular scan storedin a database (e.g., security database 212) included on fob 102. Thevascular scan information may additionally be compared with informationfrom one or more third-party databases communicating with fob 102through any communication software and/or hardware, including forexample, RFID reader 104, a USB connection, a wireless connection, acomputer, a network and/or any other means for communicating.Protocol/sequence controller 208 may facilitate the local comparison toauthenticate the biometric and authentication circuit 210 may validatethe information. Any of the embodiments may alternatively oradditionally include remote comparisons performed or controlled by oneor more third-party security vendors.

[0188] For example, for vascular pattern recognition, protocol/sequencecontroller 208 may utilize an existing database to compare the vascularscan by comparing biometric reference points, vascular coordinates,vascular and/or tissue lengths, widths and depths; blood pressureincluding waveforms, dicrotic notches, diastolic pressure, systolicpressure, anacrotic notches and pulse pressure, and/or any othercharacteristic of vascular and/or tissue patterns. This transfer ofinformation may include use of encryption, decryption, security keys,digital certificates and/or other security devices to confirm thesecurity of the sample. Fob 102 may additionally communicate withthird-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.Further, the present invention anticipates use of one or morethird-party devices such as vascular pattern recognition software and/orhardware systems to facilitate vascular scan comparisons, such as, forexample VEID International, Identica and ABT Advanced BiometricTechnologies.

[0189] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of a false vascular patterns,system 1502 may be further configured to detect a thermal patternassociated with vascular patterns and/or any other secondary procedureto thwart biometric security fraud. After verifying the biometricinformation, fob 102 and RFID reader 104 may begin mutual authenticationby the methods described herein.

[0190] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using DNAbiometrics. As discussed herein, DNA biometrics may include recognitionof structures, gene sequences, and other genetic characteristics of skintissue, hair tissue, and/or any other human tissue and/or any portionthereof containing genetic information. As discussed herein, thesegenetic features may be collectively referred to as a “DNA scan.”Biometric security system 1502 may include a biometric sensor 1504 whichmay be configured with an infrared optical sensor, a chemical sensorand/or other hardware and/or software that facilitates capture ofbiometric data from the person such as, for example scanning, detectingor otherwise sensing a DNA scan of fob user.

[0191] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the DNA scan of the fobuser to initiate the mutual authentication process between fob 102 andRFID reader 104, and/or to provide verification of the user's identity.In one embodiment, biometric sensor 1504 of the security system 1502 maycapture a DNA scan, when a user submits genetic material to sensor 1504.Biometric sensor 1504 may be in communication with asensor/interface/driver 1506 such that sensor 1504 receives the DNA scanand transmits a signal to controller 208 to facilitate activating theoperation of fob 102. A power source (e.g., battery 1503) may be incommunication with biometric sensor 1504 and sensor interface 1506 toprovide the desired power for operation of the biometric security systemcomponents.

[0192] Fob 102 may digitize the DNA scan based on genetic informationreference points and compare it against a digitized DNA scan stored in adatabase (e.g., security database 212) included on fob 102. The DNA scaninformation may additionally be compared with information from one ormore third-party databases communicating with fob 102 through anycommunication software and/or hardware, including for example, RFIDreader 104, a USB connection, a wireless connection, a computer, anetwork and/or any other means for communicating. Protocol/sequencecontroller 208 may facilitate the local comparison to authenticate thebiometric and authentication circuit 210 may validate the information.Any of the embodiments may alternatively or additionally include remotecomparisons performed or controlled by one or more third-party securityvendors.

[0193] For example, for DNA recognition, protocol/sequence controller208 may utilize an existing database to compare the DNA scan bycomparing nucleotides, code sequences, regulatory regions, initiationand stop codons, exon/intron borders, and/or any other characteristicsof DNA. This transfer of information may include use of encryption,decryption, security keys, digital certificates and/or other securitydevices to confirm the security of the sample. Fob 102 may additionallycommunicate with third-party databases to facilitate a comparisonbetween fob 102 identifier and other fob identifiers stored with thebiometric samples. Further, the present invention anticipates use of oneor more third-party devices such as DNA recognition software and/orhardware systems to facilitate DNA scan comparisons, such as, forexample Applied DNA Sciences.

[0194] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use false DNA, system 1502 may befurther configured to take a DNA sample directly off a user and/or anyother secondary procedure to thwart biometric security fraud. Afterverifying the biometric information, fob 102 and RFID reader 104 maybegin mutual authentication by the methods described herein.

[0195] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using handgeometry biometrics. As discussed herein, hand geometry biometrics mayinclude recognition of hand geometry parameters, such as, for example,hand shape, finger length, finger thickness, finger curvature and/or anyportion thereof. As discussed herein, these hand geometry features maybe collectively referred to as a “hand geometry scan.” Biometricsecurity system 1502 may include a biometric sensor 1504 which may beconfigured with an infrared optical sensor, a three-dimensional imagingsystem and/or other hardware and/or software that facilitates capture ofbiometric data from the person such as, for example scanning, detectingor otherwise sensing a hand geometry scan of fob user.

[0196] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the hand geometry scan ofthe fob user to initiate the mutual authentication process between fob102 and RFID reader 104, and/or to provide verification of the user'sidentity. In one embodiment, biometric sensor 1504 of the securitysystem 1502 may capture a hand geometry scan, when a user places hishand in front of an optical scanner. Biometric sensor 1504 may be incommunication with a sensor/interface/driver 1506 such that sensor 1504receives the hand geometry scan and transmits a signal to controller 208to facilitate activating the operation of fob 102. A power source (e.g.,battery 1503) may be in communication with biometric sensor 1504 andsensor interface 1506 to provide the desired power for operation of thebiometric security system components.

[0197] Fob 102 may digitize the hand geometry scan based on handgeometry parameters and compare it against a digitized hand geometryscan stored in a database (e.g., security database 212) included on fob102. The hand geometry scan information may additionally be comparedwith information from one or more third-party databases communicatingwith fob 102 through any communication software and/or hardware,including for example, RFID reader 104, a USB connection, a wirelessconnection, a computer, a network and/or any other means forcommunicating. Protocol/sequence controller 208 may facilitate the localcomparison to authenticate the biometric and authentication circuit 210may validate the information. Any of the embodiments may alternativelyor additionally include remote comparisons performed or controlled byone or more third-party security vendors.

[0198] For example, for hand geometry recognition, protocol/sequencecontroller 208 may utilize an existing database to compare hand shape,finger length, finger thickness, finger curvature and/or any other ofthe 90 different hand geometry parameters known in the art. Thistransfer of information may include use of encryption, decryption,security keys, digital certificates and/or other security devices toconfirm the security of the sample. Fob 102 may additionally communicatewith third-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.Further, the present invention anticipates use of one or morethird-party devices such as hand geometry recognition software and/orhardware systems to facilitate hand geometry scan comparisons, such as,for example IR Recognition Services and Human Recognition Services.

[0199] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of false hands, system 1502 may befurther configured to measure blood flow, to detect body heat and/or anyother secondary procedure to thwart biometric security fraud. Afterverifying the biometric information, fob 102 and RFID reader 104 maybegin mutual authentication by the methods described herein.

[0200] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using auditoryemissions biometrics. As discussed herein, auditory emissions biometricsmay include emissions that an ear generates when stimulated by sound,such as vibrations and reverberated sound waves and/or any portionthereof. As discussed herein, these auditory emissions features may becollectively referred to as an “auditory emissions scan.” Biometricsecurity system 1502 may include a biometric sensor 1504 which may beconfigured with an infrared optical sensor, an auditory sensor, anauditory generator and/or other hardware and/or software thatfacilitates the capture of biometric data from the person such as, forexample sound generating, scanning, detecting or otherwise sensing anauditory emissions scan of fob user.

[0201] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the auditory emissionsscan of the fob user to initiate the mutual authentication processbetween fob 102 and RFID reader 104, and/or to provide verification ofthe user's identity. In one embodiment, biometric sensor 1504 of thesecurity system 1502 may capture an auditory emissions scan, when a userhears an auditory stimulant and the user's auditory emissions aredetected by biometric sensor 1504. Biometric sensor 1504 may be incommunication with a sensor/interface/driver 1506 such that sensor 1504receives the auditory emissions scan and transmits a signal tocontroller 208 to facilitate activating the operation of fob 102. Apower source (e.g., battery 1503) may be in communication with biometricsensor 1504 and sensor interface 1506 to provide the desired power foroperation of the biometric security system components.

[0202] Fob 102 may digitize the auditory emissions scan based onemissions waveforms and compare it against a digitized auditoryemissions scan stored in a database (e.g., security database 212)included on fob 102. The auditory emissions scan information mayadditionally be compared with information from one or more third-partydatabases communicating with fob 102 through any communication softwareand/or hardware, including for example, RFID reader 104, a USBconnection, a wireless connection, a computer, a network and/or anyother means for communicating. Protocol/sequence controller 208 mayfacilitate the local comparison to authenticate the biometric andauthentication circuit 210 may validate the information. Any of theembodiments may alternatively or additionally include remote comparisonsperformed or controlled by one or more third-party security vendors.

[0203] For example, for auditory emissions recognition,protocol/sequence controller 208 may utilize an existing database tocompare emissions difference in frequency, wavelength, and/or othercharacteristics between the transmitted and reverberated sound waves.This transfer of information may include use of encryption, decryption,security keys, digital certificates and/or other security devices toconfirm the security of the sample. Fob 102 may additionally communicatewith third-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.Further, the present invention anticipates use of one or morethird-party devices such as auditory emissions recognition softwareand/or hardware systems to facilitate auditory emissions scancomparisons, such as, for example those developed by the University ofSouthampton.

[0204] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of false auditory emissions scans,system 1502 may be further configured to detect electronic noiseassociated with a device producing electronic auditory emissions and/orany other secondary procedure to thwart biometric security fraud. Afterverifying the biometric information, fob 102 and RFID reader 104 maybegin mutual authentication by the methods described herein.

[0205] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using olfactorybiometrics. As discussed herein, olfactory biometrics may includeodorants that a body generates when odor evaporates from and/or anyportion thereof. As discussed herein, these odorants may be collectivelyreferred to as a “smellprint.” Biometric security system 1502 mayinclude a biometric sensor 1504 which may be configured with anelectronic sensor, a chemical sensor, and/or an electronic or chemicalsensor configured as an array of chemical sensors, wherein each chemicalsensor may detect a specific odorant, or smell. In another embodiment,biometric sensor 1504 may be configured as a gas chromatograph,spectrometer, conductivity sensor, piezoelectric sensor and/or otherhardware and/or software that facilitates the capture of biometric datafrom the person such as, for example, scanning, detecting or otherwisesensing a smellprint of fob user.

[0206] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the smellprint of the fobuser to initiate the mutual authentication process between fob 102 andRFID reader 104, and/or to provide verification of the user's identity.In one embodiment, biometric sensor 1504 of the security system 1502 maycapture a smellprint, when a user stands within at least two feet ofsensor 1504. Biometric sensor 1504 may be in communication with asensor/interface/driver 1506 such that sensor 1504 receives thesmellprint and transmits a signal to controller 208 to facilitateactivating the operation of fob 102. A power source (e.g., battery 1503)may be in communication with biometric sensor 1504 and sensor interface1506 to provide the desired power for operation of the biometricsecurity system components.

[0207] Fob 102 may digitize the smellprint and compare it against adigitized smellprint stored in a database (e.g., security database 212)included on fob 102. The smellprint information may additionally becompared with information from one or more third-party databasescommunicating with fob 102 through any communication software and/orhardware, including for example, RFID reader 104, a USB connection, awireless connection, a computer, a network and/or any other means forcommunicating. Protocol/sequence controller 208 may facilitate the localcomparison to authenticate the biometric and authentication circuit 210may validate the information. Any of the embodiments may alternativelyor additionally include remote comparisons performed or controlled byone or more third-party security vendors.

[0208] For example, for smellprints, protocol/sequence controller 208may utilize an existing database to compare the difference in molecularstructures, chemical compounds, temperature, mass differences, pressure,force, and odorants by using statistical, ANN and neuromorphictechniques. This transfer of information may include use of encryption,decryption, security keys, digital certificates and/or other securitydevices to confirm the security of the sample. Fob 102 may additionallycommunicate with third-party databases to facilitate a comparisonbetween fob 102 identifier and other fob identifiers stored with thebiometric samples. Further, the present invention anticipates use of oneor more third-party devices such as smellprint recognition softwareand/or hardware systems to facilitate smellprint comparisons, such as,for example those developed by Company Mastiff Electronic Systems.

[0209] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of a false odorant, system 1502 maybe further configured to detect man-made smells, abnormal odorants, bodyheat and/or any other secondary procedure to thwart biometric securityfraud. After verifying the biometric information, fob 102 and RFIDreader 104 may begin mutual authentication by the methods describedherein.

[0210] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security usingkeystroke/typing recognition biometrics. As discussed herein,keystroke/typing recognition biometrics may include recognition of theduration of keystrokes, latencies between keystrokes, inter-keystroketimes, typing error frequency, force keystrokes and/or any portionthereof. As discussed herein, these features may be collectivelyreferred to as a “keystroke scan.” Biometric security system 1502 mayinclude a biometric sensor 1504 which may be configured with anelectronic sensor, an optical sensor, a keyboard, and/or other hardwareand/or software that facilitates the capture of biometric data from theperson such as, for example, scanning, detecting or otherwise sensing akeystroke scan of fob user.

[0211] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the keystroke scan of thefob user to initiate the mutual authentication process between fob 102and RFID reader 104, and/or to provide verification of the user'sidentity. In one embodiment, biometric sensor 1504 of the securitysystem 1502 may capture a keystroke scan, when a user types, forexample, a PIN or pass phrase into a keyboard configured with sensor1504. Biometric sensor 1504 may be in communication with asensor/interface/driver 1506 such that sensor 1504 receives thekeystroke scan and transmits a signal to controller 208 to facilitateactivating the operation of fob 102. A power source (e.g., battery 1503)may be in communication with biometric sensor 1504 and sensor interface1506 to provide the desired power for operation of the biometricsecurity system components.

[0212] Fob 102 may digitize the keystroke scan based on keystrokecharacteristics and compare the scan against a digitized keystroke scanstored in a database (e.g., security database 212) included on fob 102.The keystroke scan information may additionally be compared withinformation from one or more third-party databases communicating withfob 102 through any communication software and/or hardware, includingfor example, RFID reader 104, a USB connection, a wireless connection, acomputer, a network and/or any other means for communicating.Protocol/sequence controller 208 may facilitate the local comparison toauthenticate the biometric and authentication circuit 210 may validatethe information. Any of the embodiments may alternatively oradditionally include remote comparisons performed or controlled by oneor more third-party security vendors.

[0213] For example, for keystroke scans, protocol/sequence controller208 may utilize an existing database to compare the behavioral, temporaland physical characteristics associated with keystrokes. This transferof information may include use of encryption, decryption, security keys,digital certificates and/or other security devices to confirm thesecurity of the sample. Fob 102 may additionally communicate withthird-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.Further, the present invention anticipates use of one or morethird-party devices such as keystroke scan recognition software and/orhardware systems to facilitate keystroke scan comparisons, such as, forexample those developed by BioPassword® by BioNet Systems, LLC.

[0214] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of a false keystroke, system 1502may be further configured to detect body heat and/or any other secondaryprocedure to thwart biometric security fraud. After verifying thebiometric information, fob 102 and RFID reader 104 may begin mutualauthentication by the methods described herein.

[0215] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using iris scanbiometrics. As discussed herein, iris scan biometrics may includerecognition of characteristics of the colored tissues surrounding thepupil, such as the rings, furrows and freckles and/or any portionthereof. As discussed herein, these characteristics may be collectivelyreferred to as an “iris scan.” Biometric security system 1502 mayinclude a biometric sensor 1504 which may be configured with a videocamera, an optical scanner, a digital camera, a charge coupled deviceand/or other hardware and/or software that facilitates the capture ofbiometric data from the person such as, for example, scanning, detectingor otherwise sensing an iris scan of fob user.

[0216] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the iris scan of the fobuser to initiate the mutual authentication process between fob 102 andRFID reader 104, and/or to provide verification of the user's identity.In one embodiment, biometric sensor 1504 of the security system 1502 maycapture an iris scan, when a user uses sensor 1504 to scan his iriswhile he is up to five feet away from sensor 1504. Sensor 1504 may scanthe user's iris through contacts, sunglasses, and/or any other type ofeye glasses. Biometric sensor 1504 may be in communication with a sensorinterface/driver 1506 such that sensor 1504 receives the iris scan andtransmits a signal to controller 208 to facilitate activating theoperation of fob 102. A power source (e.g., battery 1503) may be incommunication with biometric sensor 1504 and sensor interface 1506 toprovide the desired power for operation of the biometric security systemcomponents.

[0217] Fob 102 may digitize the iris scan based on iris characteristicsand compare the scan against a digitized iris scan stored in a database(e.g., security database 212) included on fob 102. The iris scaninformation may additionally be compared with information from one ormore third-party databases communicating with fob 102 through anycommunication software and/or hardware, including for example, RFIDreader 104, a USB connection, a wireless connection, a computer, anetwork and/or any other means for communicating. Protocol/sequencecontroller 208 may facilitate the local comparison to authenticate thebiometric and authentication circuit 210 may validate the information.Any of the embodiments may alternatively or additionally include remotecomparisons performed or controlled by one or more third-party securityvendors.

[0218] For example, for iris scans, protocol/sequence controller 208 mayutilize an existing database to compare the surface patterns of the irisby localizing the boundaries and the eyelid contours of the iris andcreating a phase code for the texture sequence in the iris. Thistransfer of information may include use of encryption, decryption,security keys, digital certificates and/or other security devices toconfirm the security of the sample. Fob 102 may additionally communicatewith third-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.Further, the present invention anticipates use of one or morethird-party devices such as iris scan recognition software and/orhardware systems to facilitate iris scan comparisons, such as, forexample those developed by Iridian, LG Electronics and BioCom.

[0219] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of a false iris, system 1502 may befurther configured to vary the light shone into the eye to watch forpupil dilation, to detect body heat and/or any other secondary procedureto thwart biometric security fraud. After verifying the biometricinformation, fob 102 and RFID reader 104 may begin mutual authenticationby the methods described herein.

[0220] In another exemplary embodiment, biometric security system 1502may be configured for facilitating biometric security using retinalscanning biometrics. As discussed herein, retinal scanning biometricsmay include recognition of characteristics of the reflected retinalpattern of the eye, such as the location, structure, size, and shape ofblood vessels and/or any portion thereof. As discussed herein, thesecharacteristics may be collectively referred to as a “retinal scan.”Biometric security system 1502 may include a biometric sensor 1504 whichmay be configured with low-intensity light source, such as an infraredsource, an optical coupler and/or other hardware and/or software thatfacilitates the capture of biometric data from the person such as, forexample, scanning, detecting or otherwise sensing a retinal scan of fobuser.

[0221] In one exemplary application of fob 102 incorporating biometricsecurity system 1502, system 1502 may capture the iris scan of the fobuser to initiate the mutual authentication process between fob 102 andRFID reader 104, and/or to provide verification of the user's identity.In one embodiment, biometric sensor 1504 of the security system 1502 maycapture a retinal scan, when a sensor 1504 shines a light source intothe user's retina and detects the reflected retina pattern. Sensor 1504may detect a user's retinal pattern when the user is up to five feetaway from sensor 1504. Biometric sensor 1504 may be in communicationwith a sensor interface/driver 1506 such that sensor 1504 receives theretinal scan and transmits a signal to controller 208 to facilitateactivating the operation of fob 102. A power source (e.g., battery 1503)may be in communication with biometric sensor 1504 and sensor interface1506 to provide the desired power for operation of the biometricsecurity system components.

[0222] Fob 102 may digitize the retinal scan based on retinalcharacteristics and compare the scan against a digitized iris scanstored in a database (e.g., security database 212) included on fob 102.The retinal scan information may additionally be compared withinformation from one or more third-party databases communicating withfob 102 through any communication software and/or hardware, includingfor example, RFID reader 104, a USB connection, a wireless connection, acomputer, a network and/or any other means for communicating.Protocol/sequence controller 208 may facilitate the local comparison toauthenticate the biometric and authentication circuit 210 may validatethe information. Any of the embodiments may alternatively oradditionally include remote comparisons performed or controlled by oneor more third-party security vendors.

[0223] For example, for retinal scans, protocol/sequence controller 208may utilize an existing database to compare the blood vessel patterns ofthe retina by comparing stored and detected retinal patterns. Thistransfer of information may include use of encryption, decryption,security keys, digital certificates and/or other security devices toconfirm the security of the sample. Fob 102 may additionally communicatewith third-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.Further, the present invention anticipates use of one or morethird-party devices such as retinal scan recognition software and/orhardware systems to facilitate keystroke scan comparisons, such as, forexample those developed by EyeKey and Retinal Technologies.

[0224] Fob 102 and/or any other third-party security vendor system usedin connection with fob 102 may additionally be configured with secondarysecurity procedures to confirm that fake biometric samples are not beingused. For example, to detect the use of a false retina, system 1502 maybe further configured to vary the light shone into the eye to watch forpupil dilation, to detect body heat and/or any other secondary procedureto thwart biometric security fraud. After verifying the biometricinformation, fob 102 and RFID reader 104 may begin mutual authenticationby the methods described herein.

[0225] In an additional or alternate embodiment, RFID reader 104 mayinclude one or more security system, wherein the security systemincorporates one or more biometric system. As shown in FIG. 16, RFIDreader 104 includes a biometric security system 1602 configured forfacilitating biometric security using a biometric sample. Biometricsecurity system 1602 may include a biometric sensor 1604 which may beconfigured with a sensor, video camera, digital camera, optical scanner,light source and/or other hardware and/or software for acquiringbiometric data form the person such as, for example, optical scanning,chemical sensing, or otherwise detecting the portion of fob user.Biometric sensor 1604 may be in communication with a sensorinterface/driver 1606 such that sensor interface 1606 receives biometricinformation and transmits a signal to controller 208 to facilitateactivating the operation of fob 102.

[0226] In one exemplary application of RFID reader 104 includingbiometric security system 1602, the user may submit a biometric sampleto the biometric sensor to initiate the mutual authentication processbetween fob 102 and RFID reader 104, and/or to provide verification ofthe user's identity. RFID reader 104 may digitize the sample and compareit against a digitized biometric sample stored in a database (e.g.,database 310) included on RFID reader 104. The biometric sampleinformation may additionally be compared with information from one ormore third-party databases communicating with fob 102 through anycommunication software and/or hardware, including for example, fob 102,a USB connection, a wireless connection, a computer, a network and/orany other means for communicating. The transfer of information mayinclude use of encryption decryption, security keys, digitalcertificates and/or other security devices to confirm the security ofthe sample. RFID reader 104 may additionally communicate withthird-party databases to facilitate a comparison between fob 102identifier and other fob identifiers stored with the biometric samples.

[0227] Protocol/sequence controller 314 may facilitate the localcomparison to authenticate the biometric sample and authenticationcircuit 308 may validate the information. Any of the embodiments mayalternatively or additionally include remote comparisons performed orcontrolled by third-party security vendors in any way known in the artfor comparing biometric data.

[0228] RFID reader 104 may also be configured with secondary securityprocedures biometric to confirm that fake biometric samples are notbeing used. For example, RFID reader 104 may be further configured tomeasure blood flow, body heat and/or any other secondary procedure toreduce biometric security fraud. Other security procedures for ensuringthe authenticity of biometric samples may include monitoring pupildilation for retinal and/or iris scans, pressure sensors, blinkingsensors, human motion sensors, and/or any other procedures known in theart for authenticating the authenticity of biometric samples. Afterverifying the biometric information, fob 102 and RFID reader 104 maybegin mutual authentication, and the transaction may proceedaccordingly.

[0229] While the biometric safeguard mechanisms describe fob 102 and/orRFID reader 104 configured with a biometric safeguard mechanism, anypart of system 100 may be equipped with a biometric safeguard system.For example, the invention contemplates receiving a biometric sampleonly at the reader, only at the fob, at both the fob and the reader, orat any other combination of location or device. As such, any scanner ordatabase discussed herein may be located within or associated withanother device. For example, the fob may scan a user biometric, but thedatabase used for comparison may be located within the reader ormerchant server. In other embodiments, the biometric security device maybe located away from the point of sale device and/or provide otherfunctions. For example, the biometric security device may be locatednear the item to be purchased or located in any other location within oroutside of the merchant. In one embodiment, the biometric securitydevice may be located outside of a jewelry display to allow a user tonot only start the authentication process before check-out, but also toallow access to the product within the display case. In this regard, thebiometric security device may communicate the information to the pointof sale device so the POS may verify that the person that entered thejewelry box is the same person that is now buying the jewelry. Inanother embodiment, any portion of system 100 may be configured with abiometric security device. The biometric security device may be attachedand/or free-standing. Biometric security devices may be configured forlocal and/or third-party operation. For example, the present inventioncontemplates the use of third-party fingerprint scanning and securitydevices such as those made by Interlink Electronics, Keytronic, IdentixBiotouch, BIOmetricID, on Click, and/or other third-party vendors.

[0230] In yet another embodiment, the database used for comparison maycontain terrorist and/or criminal information. As used herein,terrorists and/or criminals may include terrorists, felons, criminals,convicts, indicted persons, insurgents, revolutionaries and/or otheroffenders. The information may include biometric information, personalinformation as described herein, arrest records, aliases used, countryof residence, affiliations with gangs and terrorist groups, and/or anyother terrorist and/or criminal information.

[0231] As an example of a secondary security procedure in accordancewith the present invention, the biometric sensor 1504, 1604 may beconfigured to allow a finite number of scans. For example, biometricsensor 1504, 1604 may be configured to only accept data from a singlescan. As a result, biometric sensor 1504, 1604 may turn off ordeactivate fob 102 and/or RFID reader 104 if more than one scan isneeded to obtain a biometric sample. Biometric sensor 1504, 1604 mayalso be configured to accept a preset limit of scans. For example,biometric sensor 1504, 1604 may receive three invalid biometric samplesbefore it turns off and/or deactivates fob 102 and/or RFID reader 104.

[0232] The sensor or any other part of system 100 may also activate uponsensing a particular type or group of biometric samples. The activationmay include sending a signal, blinking, audible sound, visual displayand/or the like. For example, if the sensor detects information from agold card member, the system may display a special offer on the POSterminal. If the sensor detects a repeat customer, the sensor may signalor notify a manager to approach the customer and thank them for theirrepeat business. In another embodiment, the system may send a signal toa primary account holder or any other person or device to notify themthat the fob is being used or that a condition or rule is being violated(e.g., charge above $1000).

[0233] Any of the biometric security systems described herein mayadditionally be configured with a fraud protection log. That is, abiometric security system, such as biometric security system 1502, 1602may be configured to log all biometric samples submitted on fob 102and/or RFID reader 104 and store the log information on databases onand/or communicating with system 1502, 1602. If a new and/or differentbiometric sample is submitted that differs from the log data, biometricsecurity system 1502, 1602 may employ a security procedure such asdeactivation, warning authorities, requesting a secondary scan, and/orany other security procedure.

[0234] Biometric security system 1502, 1602 and/or the biometricsecurity system configured with system 100 may also be configured toobtain a plurality of biometric samples for verification and/or othersecurity purposes. For example, after biometric security system 1502,receives a first biometric sample (e.g., scans one finger,) it may beconfigured to receive a second biometric sample (e.g., scans a secondfinger). The first and second biometric samples may be compared withstored biometric samples by any of the methods disclosed herein. Thesecond biometric sample may be the only sample compared with storedbiometric samples if the first sample is unreadable or inadequate.

[0235] In yet another exemplary embodiment of the present invention, fob102 may be equipped with a biometric safeguard mechanism. For example,in one exemplary application of fob 102, fob 102 may use biometricsecurity system 1502 to authorize a transaction that violates anestablished rule, such as, for example, a purchase exceeding anestablished per purchase spending limit, a purchase exceeding a presetnumber of transactions, any portion of a purchase and/or transactioninvolving non-monetary funds (e.g., paying a portion of the transactionwith loyalty points, coupons, airline miles, etc.) and/or any otherpurchase and/or transaction exceeding a preset or established limit. Fobuser, a third-party issuer system a third-party financial system, acompany and/or any other entity or system may establish the presetlimits. The limits may be used to prevent fraud, theft, overdrafts,and/or other non-desirable situations associated with financial andnon-financial accounts. For example, if fob 102 is stolen and the thieftries to make a large purchase with the card, the biometric safeguardmechanism may prevent the purchase until fob user's identity is verifiedby biometric means.

[0236] For example, fob 102 may activate biometric security system 1502to notify a user who is attempting to make a large purchase that theuser must provide a biometric sample to verify the user's identity. Bynotifying, fob 102 may be configured to provide an audible signal,visual signal, optical signal, mechanical signal, vibration, blinking,signaling and beeping, and/or provide any other notification to a user.Accordingly, fob user may provide such verification by submitting abiometric sample, for example placing his finger over biometric sensor1504 and/or any other biometric security devices used in associationwith fob 102. Biometric sensor 1504 may then digitize the biometricsample (e.g., fingerprint) and use the digitized sample for verificationby any of the methods described herein. Once fob user's identity and/orfob 102 transponder identifier are verified, fob 102 may provide atransaction authorized signal to RF transponder 202 (and/or totransponder 220) for forwarding to RFID reader 104. RFID reader 104 maythen provide the transaction authorized signal to POS device 110 insimilar manner as is done with conventional PIN driven systems and POSdevice 110 may process the transaction under the merchant's business asusual standard. If fob 102 has been stolen, then fob user's identity maynot be verified and the transaction may be cancelled. Additionally, oneor more further security procedures may be triggered, such as, forexample, fob 102 may deactivate, fob 102 may send a notification to asecurity vendor, fob 102 may be confiscated by the merchant and/or anyother security procedures may be used.

[0237] In another exemplary embodiment, RFID reader 104 may be equippedwith a biometric safeguard mechanism. For example, in one exemplaryapplication of RFID reader 104, RFID reader 104 may use biometricsecurity system 1602 to authorize a transaction that violates anestablished rule, such as, for example, a purchase exceeding anestablished per purchase spending limit, a purchase exceeding a presetnumber of transactions and/or any other purchase exceeding a preset orestablished limit. Fob user, a third-party issuer system a third-partyfinancial system, a company and/or any other entity or system mayestablish the preset limits. The limits may be used to prevent fraud,theft, overdrafts, and/or other non-desirable situations associated withfinancial and non-financial accounts. For example, if fob 102 is stolenand the thief tries to make a large purchase with the card, thebiometric safeguard mechanism may prevent the purchase until fob user'sidentity is verified by biometric means.

[0238] In one example, where fob user is using a company-issued fob 102,fob 102 may the have a pre-set limit of transactions that may becompleted before biometric verification is required. If the user exceedsthe transaction limit, RFID reader 104 may be configured to scan abiometric sample in order to verify the user's identity. Accordingly,the user may provide such verification by submitting a biometric sample,for example submitting a retinal scan to biometric sensor 1604. RFIDreader 104 may then digitize the biometric sample (e.g., retinalpattern) and use the digitized sample for verification by any of themethods described herein. Once fob user's identity and/or fob 102transponder identifier are verified, RFID reader 104 may receive atransaction authorized signal from a security vendor authorized to givesuch a signal. RFID reader 104 may then provide the transactionauthorized signal to POS device 110 in similar manner as is done withconvention PIN driven systems and POS device 110 may process thetransaction under the merchant's business as usual standard.

[0239] While the biometric safeguard mechanisms described herein usefingerprint scanning and retinal scanning for biometric sampleverification for exemplification, any biometric sample may be submittedfor verification, authorization and/or any other safeguard purpose. Forexample the present invention contemplates the use of voice recognition,facial and/or ear recognition, signature recognition, vascular patterns,DNA sampling, hand geometry, auditory emissions recognition, olfactoryrecognition, keystroke/typing recognition, iris scans, and/or any otherbiometric known in the art.

[0240] The preceding detailed description of exemplary embodiments ofthe invention makes reference to the accompanying drawings, which showthe exemplary embodiment by way of illustration. While these exemplaryembodiments are described in sufficient detail to enable those skilledin the art to practice the invention, it should be understood that otherembodiments may be realized and that logical and mechanical changes maybe made without departing from the spirit and scope of the invention.For example, the steps recited in any of the method or process claimsmay be executed in any order and are not limited to the order presented.Further, the present invention may be practiced using one or moreservers, as necessary. Thus, the preceding detailed description ispresented for purposes of illustration only and not of limitation, andthe scope of the invention is defined by the preceding description, andwith respect to the attached claims.

[0241] Benefits, other advantages, and solutions to problems have beendescribed above with regard to specific embodiments. However, thebenefits, advantages, solutions to problems, and any element(s) that maycause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as critical, required, or essentialfeatures or elements of any or all the claims. As used herein, the terms“comprises,” “comprising,” or any other variations thereof, are intendedto cover a nonexclusive inclusion, such that a process, method, article,or apparatus that comprises a list of elements does not include onlythose elements but may include other elements not expressly listed orinherent to such process, method, article, or apparatus. Further, noelement described herein is required for the practice of the inventionunless expressly described as “essential” or “critical.”

1. A method for registering biometric information for use in atransponder-reader system, said method comprising: detecting a profferedbiometric at a sensor to obtain a proffered biometric sample; verifyingsaid proffered biometric sample; and storing said proffered biometricsample on a database such that said system utilizes said profferedbiometric sample to authorize a transponder transaction.
 2. The methodof claim 1, wherein said step of detecting includes at least one of:detecting, associating, and processing a proffered biometric sample. 3.The method of claim 1, wherein said step of detecting includes loggingeach proffered biometric sample.
 4. The method of claim 1, wherein saidstep of detecting includes at least one of detecting, associating, andprocessing at least one additional proffered biometric sample.
 5. Themethod of claim 1, wherein said step of verifying a biometric samplefurther includes at least one of: processing, comparing, and verifyingsaid biometric sample.
 6. The method of claim 1, wherein said step ofverifying includes comparing a proffered biometric sample with a storedbiometric sample.
 7. The method of claim 6, wherein comparing aproffered biometric sample with a stored biometric sample includescomparing a proffered biometric sample with at least one of a biometricsample of a criminal, a terrorist, and a transponder user.
 8. The methodof claim 1, wherein said step of verifying includes verifying aproffered biometric sample using information contained on at least oneof a local database, a remote database, and a third-party controlleddatabase.
 9. The method of claim 1, wherein said step of verifyingincludes verifying a proffered biometric sample using one of aprotocol/sequence controller and a third-party security vendor.
 10. Themethod of claim 1, wherein said step of verifying a biometric samplefurther includes facilitating the use of one or more secondary securityprocedures.
 11. The method of claim 1, wherein said step of storing abiometric sample includes storing a proffered biometric sample on atleast one of a local database, a remote database, and a third-partycontrolled database.